From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: mst@redhat.com, eric.dumazet@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kubakici@wp.pl
Subject: Re: [PATCH net-next V2 1/3] tap: use build_skb() for small packet
Date: Wed, 16 Aug 2017 09:30:54 -0700 (PDT) [thread overview]
Message-ID: <20170816.093054.959220457289425520.davem@davemloft.net> (raw)
In-Reply-To: <3b66193a-2df1-0191-0785-20123e38460a@redhat.com>
From: Jason Wang <jasowang@redhat.com>
Date: Wed, 16 Aug 2017 17:17:45 +0800
> It looks like full page allocation just produce too much stress on the
> page allocator.
>
> I get 1.58Mpps (full page) vs 1.95Mpps (page frag) with the patches
> attached.
Yes, this is why drivers doing XDP tend to drift towards implementing
a local cache of pages.
next prev parent reply other threads:[~2017-08-16 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:41 [PATCH net-next V2 0/3] XDP support for tap Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 1/3] tap: use build_skb() for small packet Jason Wang
2017-08-16 3:45 ` Eric Dumazet
2017-08-16 3:55 ` Michael S. Tsirkin
2017-08-16 3:57 ` Jason Wang
2017-08-16 3:59 ` Michael S. Tsirkin
2017-08-16 4:07 ` Jason Wang
2017-08-16 9:17 ` Jason Wang
2017-08-16 16:30 ` David Miller [this message]
2017-08-16 3:55 ` Jason Wang
2017-08-16 10:24 ` Eric Dumazet
2017-08-16 13:16 ` Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 2/3] net: export some generic xdp helpers Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 3/3] tap: XDP support Jason Wang
2017-08-11 23:12 ` Jakub Kicinski
2017-08-12 2:48 ` Jason Wang
2017-08-14 16:01 ` Michael S. Tsirkin
2017-08-15 5:02 ` Jason Wang
2017-08-16 3:45 ` Michael S. Tsirkin
2017-08-14 8:43 ` Daniel Borkmann
2017-08-15 4:55 ` Jason Wang
2017-08-14 2:56 ` [PATCH net-next V2 0/3] XDP support for tap 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=20170816.093054.959220457289425520.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=kubakici@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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).