Messages in this thread | | | Date | Fri, 10 Oct 2003 00:57:03 -0700 | From | "David S. Miller" <> | Subject | Re: [PATCH][RFC] relayfs (1/4) (Documentation) |
| |
On Thu, 09 Oct 2003 13:42:09 -0400 Karim Yaghmour <karim@opersys.com> wrote:
> > James Morris wrote: > > It should be possible to make Netlink sockets mmapable (like the packet > > socket). > > So would you consider running printk on Netlink sockets? Do you think Netlink > could accomodate something as intensive as tracing? etc.
Of course it can. Look, netlink is used on routers to transfer hundreds of thousands of routing table entries in one fell swoop between a user process and the kernel every time the next hop Cisco has a BGP routing flap.
If you must have "enterprise wide client server" performance, we can add mmap() support to netlink sockets just like AF_PACKET sockets support such a thing. But I _really_ doubt you need this and unlike netlink sockets relayfs has no queueing model, whereas not only does netlink have one it's been tested in real life.
You guys are really out of your mind if you don't just take the netlink printk thing I did months ago and just run with it. When someone first told showed me this relayfs thing, I nearly passed out in disbelief that people are still even considering non-netlink solutions. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |