From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: brouer@redhat.com, Tom Herbert <tom@herbertland.com>,
Saeed Mahameed <saeedm@mellanox.com>,
netdev <netdev@vger.kernel.org>,
Tariq Toukan <tariqt@mellanox.com>, Davem <davem@davemloft.net>,
Saeed Mahameed <saeedm@dev.mellanox.co.il>
Subject: Re: [PATCH net] net/mlx5e: Do not recycle pages from emergency reserve
Date: Mon, 23 Jan 2017 10:14:55 +0100 [thread overview]
Message-ID: <20170123101455.380ef896@redhat.com> (raw)
In-Reply-To: <1485026809.16328.181.camel@edumazet-glaptop3.roam.corp.google.com>
On Sat, 21 Jan 2017 11:26:49 -0800
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > My previous measurements show approx 20℅ speedup on a UDP test with
> > delivery to remote CPU.
> >
> I find this a bit strange. When you have time (ie not while driving your
> car or during week end) please give more details, for example on message
> size.
I tested this with both 64 bytes and 1500 bytes. After I moved to 50G
and 100G testing then I don't need to use 64 bytes packets to provoke
the bottlenecks in the stack ;-)
> Was it before skb_condense() was added ?
It tested this just before skb_condense() was added. BUT
skb_condense() does not get activated when using mlx5, because uses
build_skb() ie. not using frags.
For people that don't realize this:
Eric's optimization in skb_condense() is about trading remote CPU
atomic refcnt (put_page) for copy + local CPU refcnt dec.
My measurements show cycles cost local=31 vs. remote=208, thus a
estimated saving around 177 cycles. Which is spend on calling a fairly
complex function __pskb_pull_tail(), and only works for more complex
SKBs with frags.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2017-01-23 9:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 7:03 [PATCH net] net/mlx5e: Do not recycle pages from emergency reserve Eric Dumazet
2017-01-19 19:14 ` Saeed Mahameed
2017-01-19 19:25 ` Eric Dumazet
2017-01-19 19:39 ` Saeed Mahameed
2017-01-21 18:09 ` Tom Herbert
[not found] ` <CAPe+=50xs=MMqxHPgTiGa3qytL7633Cygf_vBWuAuq=ceLyacg@mail.gmail.com>
2017-01-21 19:26 ` Eric Dumazet
2017-01-23 9:14 ` Jesper Dangaard Brouer [this message]
2017-01-24 9:21 ` Saeed Mahameed
2017-01-21 20:31 ` Saeed Mahameed
2017-01-22 17:50 ` Tom Herbert
2017-01-24 9:29 ` Saeed Mahameed
2017-01-23 8:39 ` Jesper Dangaard Brouer
2017-01-23 15:45 ` David Miller
2017-01-22 18:09 ` Tom Herbert
2017-01-20 10:28 ` Saeed Mahameed
2017-01-20 17:43 ` 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=20170123101455.380ef896@redhat.com \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=tom@herbertland.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).