All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: Gianni Tedesco <gianni@scaramanga.co.uk>
Cc: Tom Zanussi <zanussi@us.ibm.com>,
	linux-kernel@vger.kernel.org, karim@opersys.com,
	bob@watson.ibm.com
Subject: Re: [RFC][PATCH 0/5] relayfs
Date: Tue, 15 Jul 2003 12:01:31 -0500	[thread overview]
Message-ID: <16148.13163.8540.323403@gargle.gargle.HOWL> (raw)
In-Reply-To: <1058287227.377.17.camel@sherbert>

Gianni Tedesco writes:
 > On Tue, 2003-07-15 at 17:01, Tom Zanussi wrote:
 > > Gianni Tedesco writes:
 > >  > 
 > >  > Could this be used to replace mmap() packet socket, how does it compare?
 > > 
 > > I think so - you could send high volumes of packet traffic to a bulk
 > > relayfs channel and read it from the mmap'ed relayfs file in user
 > > space.  The Linux Trace Toolkit does the same thing with large volumes
 > > of trace data - you could look at that code as an example
 > > (http://www.opersys.com/relayfs/ltt-on-relayfs.html).
 > 
 > What are the semantics of the mmap'ing the buffer? With mmaped packet
 > socket the userspace (read-side) requires no sys-calls apart from when
 > the buffer is empty, it then uses poll(2) to sleep until something new
 > is put in the buffer. Can relayfs do a similar thing? poll is not
 > mentioned in the docs...

You're right - I haven't implemented poll() in the relayfs VFS code
yet.  I plan on doing that next, but won't have much time for the next
couple of weeks.  Currently, you'd have to do something like LTT does,
which is have the kernel side signal the read-side when data is ready.

Tom

 > 
 > Thanks.
 > 
 > -- 
 > // Gianni Tedesco (gianni at scaramanga dot co dot uk)
 > lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
 > 8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
 > 

-- 
Regards,

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


  reply	other threads:[~2003-07-15 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 15:15 [RFC][PATCH 0/5] relayfs Tom Zanussi
2003-07-15 15:27 ` Gianni Tedesco
2003-07-15 16:01   ` Tom Zanussi
2003-07-15 16:40     ` Gianni Tedesco
2003-07-15 17:01       ` Tom Zanussi [this message]
2003-07-15 18:45       ` Tom Zanussi
2003-07-16 21:55 ` [PATCH] relayfs Stephen Hemminger
2003-07-16 22:27   ` [PATCH] relay_open const filename Stephen Hemminger
2003-07-18 21:11   ` [PATCH] relayfs 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=16148.13163.8540.323403@gargle.gargle.HOWL \
    --to=zanussi@us.ibm.com \
    --cc=bob@watson.ibm.com \
    --cc=gianni@scaramanga.co.uk \
    --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 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.