From: Jason Wang <jasowang@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mst@redhat.com, jbrouer@redhat.com
Subject: Re: [PATCH net-next V2 0/2] XDP transmission for tuntap
Date: Wed, 10 Jan 2018 11:00:45 +0800 [thread overview]
Message-ID: <a8646e18-e9ac-84f4-dc67-8b7870551ab5@redhat.com> (raw)
In-Reply-To: <20180109.110613.1571539954764298228.davem@davemloft.net>
On 2018年01月10日 00:06, David Miller wrote:
> From: Jason Wang <jasowang@redhat.com>
> Date: Thu, 4 Jan 2018 11:14:26 +0800
>
>> This series tries to implement XDP transmission (ndo_xdp_xmit) for
>> tuntap. Pointer ring was used for queuing both XDP buffers and
>> sk_buff, this is done by encoding the type into lowest bit of the
>> pointer and storin XDP metadata in the headroom of XDP buff.
>>
>> Tests gets 3.05 Mpps when doing xdp_redirect_map from ixgbe to VM
>> (testpmd + virtio-net in guest). This gives us ~20% improvments
>> compared to use skb during redirect.
>>
>> Please review.
>>
>> Changes from V1:
>>
>> - slient warnings
>> - fix typos
>> - add skb mode number in the commit log
> Series applied, thanks Jason.
>
> There was some overlap with recent changes from Jesper, please take
> a look.
>
> Thank you.
The changes looks good, will have a test and report.
Thanks
prev parent reply other threads:[~2018-01-10 3:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 3:14 [PATCH net-next V2 0/2] XDP transmission for tuntap Jason Wang
2018-01-04 3:14 ` [PATCH net-next V2 1/2] tun/tap: use ptr_ring instead of skb_array Jason Wang
2018-01-04 3:14 ` [PATCH net-next V2 2/2] tuntap: XDP transmission Jason Wang
2018-01-10 16:11 ` Tariq Toukan
2018-01-11 2:35 ` Jason Wang
2018-01-09 16:06 ` [PATCH net-next V2 0/2] XDP transmission for tuntap David Miller
2018-01-10 3:00 ` Jason Wang [this message]
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=a8646e18-e9ac-84f4-dc67-8b7870551ab5@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=jbrouer@redhat.com \
--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).