linux-kernel - Re: select-like implementation for kernel sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-id: <463E0DD3.9050909@shaw.ca>
Date:	Sun, 06 May 2007 11:18:11 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	eitanr@...iocodes.com, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: select-like implementation for kernel sockets

eitanr@...iocodes.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@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/