mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: karim@opersys.com, 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: Mon, 13 Oct 2003 09:53:09 -0500	[thread overview]
Message-ID: <16266.48213.389446.904941@gargle.gargle.HOWL> (raw)
In-Reply-To: <20031011103429.5ebe3085.davem@redhat.com>

David S. Miller writes:
 > 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.
 > 

relayfs isn't trying to provide a generic queueing model - it's
basically just an efficient buffering mechanism with hooks for
kernel-user data transfer.  It's a lower-level thing than netlink and
might even be of use to netlink as a buffering layer.

In any case, applications like tracing or kernel debugging don't have
a need for more of a queueing model than the in-order delivery and
event buffering capabilities relayfs provides, and since applications
like these either can't use netlink or would benefit from the
efficiency provided by a no-frills buffering scheme, maybe there
is actually a use for something like relayfs.

-- 
Regards,

Tom Zanussi <zanussi@us.ibm.com>
IBM Linux Technology Center/RAS


  parent reply	other threads:[~2003-10-13 14:54 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
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 [this message]
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=16266.48213.389446.904941@gargle.gargle.HOWL \
    --to=zanussi@us.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 \
    /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

all inboxes | Powered by JetHome®