On Thursday 21 July 2005 02:55, Walker, Bruce J (HP-Labs) wrote:
> Like Lars, I too was under the wrong impression about this configfs
> "nodemanager" kernel component. Our discussions in the cluster meeting
> Monday and Tuesday were assuming it was a general service that other
> kernel components could/would utilize and possibly also something that
> could send uevents to non-kernel components wanting a std. way to see
> membership information/events.
>
> As to kernel components without corresponding user-level "managers", look
> no farther than OpenSSI. Our hope was that we could adapt to a user-land
> membership service and this interface thru configfs would drive all our
> kernel subsystems.
Guys, it is absolutely stupid to rely on a virtual filesystem for
userspace/kernel communication for any events that might have to be
transmitted inside the block IO path. This includes, among other things,
memberhips events. Inserting a virtual filesystem into this path does
nothing but add long call chains and new, hard-to-characterize memory
usage.
There are already tried-and-true interfaces that are designed to do this
kind of job efficiently and with quantifiable resource requirements:
sockets (UNIX domain or netlink) and ioctls. If you want to layer a
virtual filesystem on top as a user friendly way to present current cluster
configuration or as a way to provide some administrator knobs, then fine,
virtual filesystems are good for this kind of thing. But please do not try
to insinuate that bloat into the block IO path.
Regards,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |