From: "David S. Miller" <davem@redhat.com>
To: karim@opersys.com
Cc: jmorris@redhat.com, zanussi@us.ibm.com,
linux-kernel@vger.kernel.org, bob@watson.ibm.com
Subject: Re: [PATCH][RFC] relayfs (1/4) (Documentation)
Date: Fri, 10 Oct 2003 00:57:03 -0700 [thread overview]
Message-ID: <20031010005703.0daf3e19.davem@redhat.com> (raw)
In-Reply-To: <3F859DF1.8000602@opersys.com>
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.
next prev parent reply other threads:[~2003-10-10 7:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 20:59 Tom Zanussi
2003-10-09 13:45 ` James Morris
2003-10-09 15:25 ` Tom Zanussi
2003-10-09 17:15 ` James Morris
2003-10-09 17:42 ` Karim Yaghmour
2003-10-10 7:57 ` David S. Miller [this message]
2003-10-10 14:41 ` Karim Yaghmour
2003-10-11 17:34 ` David S. Miller
2003-10-12 23:23 ` Richard J Moore
2003-10-13 17:25 ` David S. Miller
2003-10-14 11:32 ` Richard J Moore
2003-10-14 16:44 ` David S. Miller
2003-10-15 16:56 ` Richard J Moore
2003-11-13 14:19 ` Hubertus Franke
2003-10-13 14:53 ` Tom Zanussi
2003-10-10 15:26 ` Tom Zanussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031010005703.0daf3e19.davem@redhat.com \
--to=davem@redhat.com \
--cc=bob@watson.ibm.com \
--cc=jmorris@redhat.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome