netdev - Re: [RFC 0/2] New socket API: recvmmsg

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] [day] [month] [year] [list]

Message-Id: <20090520.173036.33695641.davem@davemloft.net>
Date:	Wed, 20 May 2009 17:30:36 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	acme@...hat.com
Cc:	netdev@...r.kernel.org, vanhoof@...hat.com, williams@...hat.com
Subject: Re: [RFC 0/2] New socket API: recvmmsg

From: Arnaldo Carvalho de Melo <acme@...hat.com>
Date: Wed, 20 May 2009 20:06:42 -0300

> 	The following two patches, that I cooked today and haven't
> properly benchmarked, implements a new socket syscall, recvmmsg, that
> stands for receive multiple messages, in one call.

As I discussed with Arnaldo on IRC I am OK with this kind of
interface.

And, also, I think we need to seriously consider the patches
posted by others a few weeks ago that allowed sending to
multiple receivers in one system call.

The old adage about syscalls being cheap no longer holds when
we're talking about traversing all the way into the protocol
stack socket code every call, taking the socket lock every
time, etc.  So we really do need these batching variants of
I/O calls, or something similar.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html