netdev - Re: [RFC 1/2] net: Introduce recvmmsg socket syscall

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: <20090604014622.GI7805@ghostprotocols.net>
Date:	Wed, 3 Jun 2009 22:46:23 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Andrew Grover <andy.grover@...il.com>
Cc:	Neil Horman <nhorman@...driver.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	Chris Van Hoof <vanhoof@...hat.com>,
	Clark Williams <williams@...hat.com>
Subject: Re: [RFC 1/2] net: Introduce recvmmsg socket syscall

Em Wed, Jun 03, 2009 at 06:44:22PM -0700, Andrew Grover escreveu:
> On Fri, May 22, 2009 at 1:06 PM, Neil Horman <nhorman@...driver.com> wrote:
> > Not to throw more questions into the mix again, but didn't Ingo write a
> > batching syscall a while back, which let you issue several syscalls in one trap
> > to kernel space?  I understand that your approach has some efficiency gains over
> > that, but did that ever get accepted upstream?  Is the overlap there sufficient
> > to make this approach redundant?  Or are the gains in performance here
> > sufficient to warrant this new call?
> 
> I couldn't find this via Google or any posts to LKML by Ingo on this?
> 
> I'm very interested in multiple send/recvmsg support. So, it's
> definitely going to happen? :-)

I got sidetracked with some other activities, and was waiting for more
comments and reports from some testers, but will be back to implement a
v2 patch soon.

- Arnaldo
--
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