From: Nir Tzachar <nir.tzachar@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Linux Networking Development Mailing List
<netdev@vger.kernel.org>
Cc: Ziv Ayalon <ziv@final.co.il>
Subject: Re: [RFCv4 PATCH 2/2] net: Allow protocols to provide an unlocked_recvmsg socket method
Date: Thu, 1 Oct 2009 11:49:39 +0200 [thread overview]
Message-ID: <9b2db90b0910010249h182bf5d4sc7fdaea9e1345720@mail.gmail.com> (raw)
In-Reply-To: <20090923043813.GA6464@ghostprotocols.net>
Hi Arnaldo
I have repeated the tests using net-next on top of linus' git tree (I
hope I got it right..) and the patches you sent me. Things did not get
better, and in most cases were even worse; the recvmmsg parts
distinctly showed better throughput, but the latency has more than
doubled.
The simplest test of using a batch size of 1 results with recvmmsg's
latency over 1000 micro, while regular recvmsg is around 450 micro.
(note that to use 1 packet there is a small bug in the reg_recv which
needs to be fixed. Namely, change ret = -1 to ret = 0). On the
previous system config -- part 0001 of the patch, on top of 2.6.31 --
the latency of a single packet batch is 370 micro.
So, there seems to be a regression with the kernel tree I am using, or
with part 0002 of the path. I'll try running the net-next with only
part 1 of the patch and report.
Cheers.
next prev parent reply other threads:[~2009-10-01 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 17:07 [RFCv4 PATCH 2/2] net: Allow protocols to provide an unlocked_recvmsg socket method Arnaldo Carvalho de Melo
2009-09-17 14:09 ` Nir Tzachar
2009-09-17 21:21 ` Arnaldo Carvalho de Melo
2009-09-17 21:53 ` Arnaldo Carvalho de Melo
[not found] ` <20090923000925.GA6011@ghostprotocols.net>
[not found] ` <9b2db90b0909222123x7e547210p5755adf9f8ae875f@mail.gmail.com>
[not found] ` <20090923043813.GA6464@ghostprotocols.net>
2009-10-01 9:49 ` Nir Tzachar [this message]
2009-10-01 15:03 ` Arnaldo Carvalho de Melo
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=9b2db90b0910010249h182bf5d4sc7fdaea9e1345720@mail.gmail.com \
--to=nir.tzachar@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=netdev@vger.kernel.org \
--cc=ziv@final.co.il \
/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).