On 05. des. 2013 18:50, Arnaldo Carvalho de Melo wrote:
Em Thu, Dec 05, 2013 at 11:39:45AM +0100, David Sommerseth escreveu:
> On 05. des. 2013 10:42, Jiri Kastner wrote:
>> i like more idea of 'cutting off' oscilloscope from tuna as it has
>> more common with rt-tests then with tuna itself.
>
> Agreed! oscilloscope is really useful when joined with cyclictest. And
> that's basically the path which this patch starts.
The idea was that you tune + observe the impact of tuning.
Tuna tunes, oscilloscope shows effect of such tuning, cyclictest was
just the easiest metric generator available, but it could be any other.
Fair enough. But when considering that oscilloscope can work pretty
nicely separately makes it somewhat odd for an explicit tuna dependency.
If tuna gets more fancy in the future and implements an integrated
oscilloscope view, it would make more sense that tuna depends on
oscilloscope and not the other way around like now.
The reason for suggesting this split is also primarily packaging wise.
Especially for RHEL packaging where tuna is now a "standard" package
while oscilloscope is "optional". In addition, there's quite some
aversion among the "management layer" for packages which have an
explicit dependency between packages in "standard" and "optional".
So
it's just to get resolve these issues, without introducing too many
other challenges.
David S.