Hello,
For the cello-based io controller we are developing we need to assign certain queue-reordering functions to each class. For instance, the cello paper defines a real-time reordeding, deadline reordering and best-effort reordering. But the rcfs interface only allows to set the limit and guarantee for a class, there is no [obvious] way to set a different parameter. Are there any plans to add this capability to rcfs?
the share file, present in every class, was to contain the common set of
parameters of interest to all controllers. Hence this file is not expected to be extensible to include the per-class params.
You can use the /rcfs/taskclass/config interface to set per-controller parameters. But this will apply to all the classes, not just one.
As I was trying to work around this problem, I attempted to use the
class name to infer what the classified function should be (three
classes is good enough of a test, for starters) - but I have
discovered that the class name contains the mount point and the class
type: /rcfs/taskclass/foo/bar, when I was really expecting only the significant part of the path "foo/bar", since the mountpoint can be
anywhere and the class type can be obtained by other means. Is this
deliberate, or it just happened and nobody had a reason to change it?
The reason for using a fully qualified path serves to uniquely identify a class. Admittedly, the mount point isn't necessary, but the classtype is.
Why is the presence of a common prefix (the mount point) a problem for the classification function you're writing ?
-- Shailabh
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
