From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: "Caitlin Bestler" <caitlin.bestler@gmail.com>,
"Chris Van Hoof" <vanhoof@redhat.com>,
"Clark Williams" <williams@redhat.com>,
"Neil Horman" <nhorman@tuxdriver.com>,
"Nir Tzachar" <nir.tzachar@gmail.com>,
"Nivedita Singhvi" <niv@us.ibm.com>,
"Paul Moore" <paul.moore@hp.com>,
"Rémi Denis-Courmont" <remi.denis-courmont@nokia.com>,
"Steven Whitehouse" <steve@chygwyn.com>,
"Linux Networking Development Mailing List"
<netdev@vger.kernel.org>
Subject: Re: [RFCv4 PATCH 1/2] net: Introduce recvmmsg socket syscall
Date: Fri, 9 Oct 2009 16:35:20 -0300 [thread overview]
Message-ID: <20091009193520.GD12982@ghostprotocols.net> (raw)
In-Reply-To: <20090916170738.GC7699@ghostprotocols.net>
Em Wed, Sep 16, 2009 at 02:07:38PM -0300, Arnaldo Carvalho de Melo escreveu:
> Meaning receive multiple messages, reducing the number of syscalls and
> net stack entry/exit operations.
>
> Next patches will introduce mechanisms where protocols that want to
> optimize this operation will provide an unlocked_recvmsg operation.
Hi Dave,
The second patch in this series has issues, I still have to
investigate it properly, study removing the skb_queue_head lock like TCP
does, but the first patch seems to be OK and already providing good
results at least as reported by Nir, if there aren't any other concerns
about the API, can we get it into net-next-2.6?
Best Regards,
- Arnaldo
next prev parent reply other threads:[~2009-10-09 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 17:07 [RFCv4 PATCH 1/2] net: Introduce recvmmsg socket syscall Arnaldo Carvalho de Melo
2009-10-09 19:35 ` Arnaldo Carvalho de Melo [this message]
2009-10-09 21:27 ` David Miller
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=20091009193520.GD12982@ghostprotocols.net \
--to=acme@redhat.com \
--cc=caitlin.bestler@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nir.tzachar@gmail.com \
--cc=niv@us.ibm.com \
--cc=paul.moore@hp.com \
--cc=remi.denis-courmont@nokia.com \
--cc=steve@chygwyn.com \
--cc=vanhoof@redhat.com \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).