mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: James Morris <jmorris@redhat.com>
Cc: Tom Zanussi <zanussi@us.ibm.com>,
	linux-kernel@vger.kernel.org, <karim@opersys.com>,
	<bob@watson.ibm.com>
Subject: Re: [PATCH][RFC] relayfs (1/4) (Documentation)
Date: Thu, 9 Oct 2003 10:25:49 -0500	[thread overview]
Message-ID: <16261.32253.607756.900278@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0310090943200.13537-100000@thoron.boston.redhat.com>

James Morris writes:
 > On Tue, 7 Oct 2003, Tom Zanussi wrote:
 > 
 > > This 4-part patch contains code for an interim version of relayfs (see
 > > Documentation below for a description of relayfs).
 > 
 > What is wrong with using Netlink sockets instead of this?

Nothing, if they meet your needs.  One thing you can do with relayfs
files is mmap() them.  That combined with the kernel-side API,
designed to make writing data into buffers and transferring it as
large blocks to user-space efficient and flexible, allows for
high-speed, high-volume applications which I'm not sure Netlink was
designed for.

relayfs can also be used in 'packet' mode, using read(2) to read data
as it becomes available, so it can be used for low-speed, low-volume
applications as well.  Also, some people might find the file-based
approach more natural to deal with.  Personal preference, I suppose.

Tom


 > 
 > 
 > - James
 > -- 
 > James Morris
 > <jmorris@redhat.com>
 > 
 > 
 > 

-- 
Regards,

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


  reply	other threads:[~2003-10-09 15:27 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 [this message]
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
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=16261.32253.607756.900278@gargle.gargle.HOWL \
    --to=zanussi@us.ibm.com \
    --cc=bob@watson.ibm.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®