From: Richard J Moore <rasman@uk.ibm.com>
To: "David S. Miller" <davem@redhat.com>, 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: Sun, 12 Oct 2003 23:23:48 +0000 [thread overview]
Message-ID: <200310122323.48885.rasman@uk.ibm.com> (raw)
In-Reply-To: <20031011103429.5ebe3085.davem@redhat.com>
On Sat 11 October 2003 5:34 pm, David S. Miller wrote:
> On Fri, 10 Oct 2003 10:41:29 -0400
>
> Karim Yaghmour <karim@opersys.com> wrote:
> > The question isn't whether netlink can transfer hundreds of thousands of
> > data units in one fell swoop. The question is: is it more efficient than
> > relayfs at this?
>
> Wrong, it's the queueing model that's important for applications
> like this.
Why is a queuing model relvant to low-level kernel tracing, which is the prime
target of relayfs? In otherwords why would netlink be the infrastructure of
choice on which to implenment tracing, say in a GB ethernet driver?
> -
> 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/
--
Richard J Moore
IBM Linux Technology Centre
next prev parent reply other threads:[~2003-10-12 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 20:59 [PATCH][RFC] relayfs (1/4) (Documentation) 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
2003-10-10 14:41 ` Karim Yaghmour
2003-10-11 17:34 ` David S. Miller
2003-10-12 23:23 ` Richard J Moore [this message]
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=200310122323.48885.rasman@uk.ibm.com \
--to=rasman@uk.ibm.com \
--cc=bob@watson.ibm.com \
--cc=davem@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.