linux-kernel - Re: behavior of recvmmsg() on blocking 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <g76h4xrt5j1pw2kk3tUYAxe124vaj_firegpg@mail.gmail.com>
Date:	Wed, 24 Mar 2010 11:34:42 -0700 (PST)
From:	drepper@...il.com
To:	Brandon Black <blblack@...il.com>
Cc:	Chris Friesen <cfriesen@...tel.com>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: behavior of recvmmsg() on blocking sockets

On Wed, Mar 24, 2010 at 11:28, Brandon Black <blblack@...il.com> wrote:
> I still think having a "block until at least one packet arrives" mode
> for recvmmsg() makes sense though.

I agree.  This is the mode I've seen people asking for.  They want the call to return as quickly as possible if there is data and then with as many messages as possible.  A MSG_WAITFORONE flag would do the trick nicely.
Download attachment "signature.asc" of type "application/pgp-signature" (273 bytes)