From: David Laight <David.Laight@ACULAB.COM>
To: 'Alexander Duyck' <alexander.h.duyck@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Jiafei.Pan@freescale.com" <Jiafei.Pan@freescale.com>,
David Miller <davem@davemloft.net>,
"jkosina@suse.cz" <jkosina@suse.cz>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"LeoLi@freescale.com" <LeoLi@freescale.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: RE: [PATCH] net: use hardware buffer pool to allocate skb
Date: Fri, 17 Oct 2014 09:11:09 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1C9D895B@AcuExch.aculab.com> (raw)
In-Reply-To: <54400C6C.7010405@redhat.com>
From: Alexander Duyck
...
> Actually the likelihood of anything holding onto the 4K page for very
> long doesn't seem to occur, at least from the drivers perspective. It
> is one of the reasons why I went for the page reuse approach rather than
> just partitioning a single large page. It allows us to avoid having to
> call IOMMU map/unmap for the pages since the entire page is usually back
> in the driver ownership before we need to reuse the portion given to the
> stack.
That is almost certainly true for most benchmarks, benchmark processes
consume receive data.
But what about real life situations?
There must be some 'normal' workloads where receive data doesn't get consumed.
David
next prev parent reply other threads:[~2014-10-17 9:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 3:26 [PATCH] net: use hardware buffer pool to allocate skb Pan Jiafei
2014-10-15 4:15 ` Eric Dumazet
2014-10-15 4:26 ` David Miller
2014-10-15 5:43 ` Jiafei.Pan
2014-10-15 9:15 ` Eric Dumazet
2014-10-15 4:25 ` David Miller
2014-10-15 5:34 ` Jiafei.Pan
2014-10-15 9:15 ` Eric Dumazet
2014-10-16 2:17 ` Jiafei.Pan
2014-10-16 4:15 ` Eric Dumazet
2014-10-16 5:15 ` Jiafei.Pan
2014-10-16 15:28 ` Alexander Duyck
2014-10-16 16:57 ` Eric Dumazet
2014-10-16 17:10 ` Alexander Duyck
2014-10-16 17:45 ` Eric Dumazet
2014-10-16 18:20 ` Alexander Duyck
2014-10-16 21:40 ` Eric Dumazet
2014-10-16 22:12 ` Alexander Duyck
2014-10-17 9:11 ` David Laight [this message]
2014-10-17 14:40 ` Alexander Duyck
2014-10-17 16:55 ` Eric Dumazet
2014-10-17 18:28 ` Alexander Duyck
2014-10-17 18:53 ` Eric Dumazet
2014-10-18 0:26 ` Eric Dumazet
2014-10-17 19:02 ` Eric Dumazet
2014-10-17 19:38 ` Alexander Duyck
2014-10-17 19:51 ` Eric Dumazet
2014-10-17 22:13 ` Alexander Duyck
2014-10-17 2:35 ` Jiafei.Pan
2014-10-17 14:05 ` Eric Dumazet
2014-10-17 14:12 ` Alexander Duyck
2014-10-16 2:17 ` Jiafei.Pan
2014-10-15 15:51 ` David Miller
2014-10-15 4:59 ` Oliver Hartkopp
2014-10-15 5:47 ` Jiafei.Pan
2014-10-15 8:57 ` David Laight
2014-10-15 9:33 ` Stephen Hemminger
2014-10-16 2:30 ` Jiafei.Pan
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=063D6719AE5E284EB5DD2968C1650D6D1C9D895B@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=Jiafei.Pan@freescale.com \
--cc=LeoLi@freescale.com \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).