From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@mellanox.com>,
Or Gerlitz <gerlitz.or@gmail.com>,
Eugenia Emantayev <eugenia@mellanox.com>,
brouer@redhat.com
Subject: Re: [net-next PATCH V1 1/3] net: bulk alloc and reuse of SKBs in NAPI context
Date: Tue, 10 May 2016 16:48:57 +0200 [thread overview]
Message-ID: <20160510164857.72c8a1cb@redhat.com> (raw)
In-Reply-To: <1462888134.23934.60.camel@edumazet-glaptop3.roam.corp.google.com>
On Tue, 10 May 2016 06:48:54 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Tue, 2016-05-10 at 14:30 +0200, Jesper Dangaard Brouer wrote:
>
> > Disable busy poll on both client and server, Not patched:
> >
> > $ netperf -H 198.18.40.2 -t TCP_RR -l 60 -T 6,6 -Cc
> > MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 port 0 AF_INET to 198.18.40.2
> > () port 0 AF_INET : histogram : demo : first burst 0 : cpu bind
> > Local /Remote
> > Socket Size Request Resp. Elapsed Trans. CPU CPU S.dem S.dem
> > Send Recv Size Size Time Rate local remote local remote
> > bytes bytes bytes bytes secs. per sec % S % S us/Tr us/Tr
> >
> > 16384 87380 1 1 60.00 78077.55 3.74 2.69 3.830 8.265
> > 16384 87380
>
> Tell us more about the -T6,6
>
> For example how many TX/RX queues you have on the NIC, and which cpus
> service interrupts.
The -T6,6 option:
-T lcpu,rcpu Request netperf/netserver be bound to local/remote cpu
I use the option to get more stable results. If I don't pin/bind the
CPU netperf/netserver is running on then the CPU scheduler will migrate
the processes around. This gives unpredictable results, worst for the
busy_poll tests. Especially if the RX softirq runs on the same CPU
(also true if it runs on a HyperTread siping).
Netperf client (8 cores i7-4790K CPU @ 4.00GHz) RX:8 and TX:8 queues.
Netserver server (2x 12 cores E5-2630 @ 2.30GHz) RX:8 and TX:24 queues.
Driver mlx4.
Disabled GRO to hit code path I changed in patch 2.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2016-05-10 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:44 [net-next PATCH V1 0/3] net: enable use of kmem_cache_alloc_bulk in network stack Jesper Dangaard Brouer
2016-05-09 13:44 ` [net-next PATCH V1 1/3] net: bulk alloc and reuse of SKBs in NAPI context Jesper Dangaard Brouer
2016-05-09 16:20 ` Alexander Duyck
2016-05-09 19:59 ` Jesper Dangaard Brouer
2016-05-09 20:46 ` Alexander Duyck
2016-05-10 9:29 ` Jesper Dangaard Brouer
2016-05-10 12:30 ` Jesper Dangaard Brouer
2016-05-10 13:48 ` Eric Dumazet
2016-05-10 14:48 ` Jesper Dangaard Brouer [this message]
2016-05-10 15:44 ` Eric Dumazet
2016-05-10 17:46 ` Alexander Duyck
2016-05-09 13:44 ` [net-next PATCH V1 2/3] mlx4: use napi_alloc_skb API to get SKB bulk allocations Jesper Dangaard Brouer
2016-05-09 16:47 ` Alexander Duyck
2016-05-09 20:05 ` Jesper Dangaard Brouer
2016-05-09 13:44 ` [net-next PATCH V1 3/3] net: warn on napi_alloc_skb being called in wrong context Jesper Dangaard Brouer
2016-05-09 13:53 ` Sergei Shtylyov
2016-05-09 13:53 ` Sergei Shtylyov
2016-05-09 16:33 ` Alexander Duyck
2016-05-09 20:03 ` Jesper Dangaard Brouer
2016-05-20 8:14 ` [net-next PATCH V1 0/3] net: enable use of kmem_cache_alloc_bulk in network stack Jesper Dangaard Brouer
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=20160510164857.72c8a1cb@redhat.com \
--to=brouer@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=eugenia@mellanox.com \
--cc=gerlitz.or@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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).