public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: eitanr@audiocodes.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: select-like implementation for kernel sockets
Date: Sun, 06 May 2007 11:18:11 -0600	[thread overview]
Message-ID: <463E0DD3.9050909@shaw.ca> (raw)
In-Reply-To: <1178449075.942407.164040@q75g2000hsh.googlegroups.com>

eitanr@audiocodes.com wrote:
> Hi,
> 
> I'm using kernel sockets to Tx and Rx UDP packets between my hardware
> device (DSP) to the external network (this is part of a VoIP
> implementation). The motivation for using kernel sockets rather than
> user-space sockets is to avoid the copying of data between kernel and
> user spaces.

I think we are zero-copy in many cases for UDP these days, so this 
doesn't necessarily buy you anything..

> 
> I have no problems on the Tx side (I simply call sock_sendmsg on one
> of the sockets), but for the Rx side I want to listen-in on multiple
> sockets in blocking mode (I don't want to use polling).
> 
> Is there a way to listen-in on multiple kernel sockets from one kernel
> thread? In the user space I would have used select(), but I am not
> familiar with a similar solution for the kernel space.
> 
> Thanks,
> Eitan.
> 
> Eitan Richardson
> AudioCodes Ltd.
> 

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-05-06 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1178449075.942407.164040@q75g2000hsh.googlegroups.com>
2007-05-06 17:18 ` Robert Hancock [this message]
2007-05-07  6:57   ` select-like implementation for kernel sockets kalash nainwal
2007-05-07  8:04     ` Eitan Richardson

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=463E0DD3.9050909@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=eitanr@audiocodes.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