Messages in this thread | | | Date | Thu, 03 Jul 2008 12:18:45 +0900 | From | Tejun Heo <> | Subject | Re: [PATCH 06/11] sysfs: Implement sysfs tagged directory support. |
| |
Hello, Eric.
Eric W. Biederman wrote: >> If >> changing the default function is too much of a hassle (and I'm sure it >> would be), just add an extended version which takes @tag. The current >> implementation feels like it tried too hard to not add intermediate >> interfaces and ended up shooting outside from the innermost layer. > > It tried for something that was simple to use and that worked. > > Also the way things work. I have to use all of the intermediate layers > and their calls to various functions. So just passing a parameter through > doesn't work to well.
There is rather large possibility that I'm just being dumb here especially because I haven't reviewed the users of this facility, so all the comments I'm making are from the POV of interfaces of sysfs and the related layers. I think I've made my concerns clear by now. If you still think the callbacks are the best way to go, please try to enlighten me. I really don't wanna be stopping something which is better from ignorance. Just give me some concrete examples or point me to codes which show how and why the current interface is the best for the users and switching isn't a good idea.
> It looks to me like the clean solution is move kobject_tag into > kobj_type, and have it call some higher level function. > > We also need to remove the maintenance disaster that is > kobject_set_name from sysfs_rename_dir. And push it into > kobject_rename instead. The error handling is harder in > that case but otherwise we should be in good shape.
Heh... I personally think kobject layer as a whole should just be hidden under the cabinet of device driver model but I'm having difficult time convincing other people of it. Anyways, fully agree the interaction between kobject and sysfs is ugly at a lot of places.
>>> On the other side I can't pass a tag through from the device layer to >>> the kobject layer. It isn't a concept the kobject layer supports. >> I think it's best to make kobject layer support it. > > Assuming Greg will accept it when he sees reasonable patches.
Greg says he would. :-)
Thanks a lot for your patience.
-- tejun
| |