From: David Ahern <dsahern@gmail.com>
To: Martin Habets <mhabets@solarflare.com>,
Charles McLachlan <cmclachlan@solarflare.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com, brouer@redhat.com
Subject: Re: [PATCH net-next v4 0/6] sfc: Add XDP support
Date: Sun, 3 Nov 2019 10:24:13 -0700 [thread overview]
Message-ID: <236ff7c4-95da-da0e-8ba7-12bfb92c7d55@gmail.com> (raw)
In-Reply-To: <e3f1c071-3609-d6e7-81d6-9ee73f9f4f6a@solarflare.com>
On 11/1/19 4:07 AM, Martin Habets wrote:
> On 31/10/2019 22:18, David Ahern wrote:
>> On 10/31/19 4:21 AM, Charles McLachlan wrote:
>>> Supply the XDP callbacks in netdevice ops that enable lower level processing
>>> of XDP frames.
>>>
>>> Changes in v4:
>>> - Handle the failure to send some frames in efx_xdp_tx_buffers() properly.
>>>
>>> Changes in v3:
>>> - Fix a BUG_ON when trying to allocate piobufs to xdp queues.
>>> - Add a missed trace_xdp_exception.
>>>
>>> Changes in v2:
>>> - Use of xdp_return_frame_rx_napi() in tx.c
>>> - Addition of xdp_rxq_info_valid and xdp_rxq_info_failed to track when
>>> xdp_rxq_info failures occur.
>>> - Renaming of rc to err and more use of unlikely().
>>> - Cut some duplicated code and fix an array overrun.
>>> - Actually increment n_rx_xdp_tx when packets are transmitted.
>>>
>>
>> Something is up with this version versus v2. I am seeing a huge
>> performance drop with my L2 forwarding program - something I was not
>> seeing with v2 and I do not see with the experimental version of XDP in
>> the out of tree sfc driver.
>>
>> Without XDP:
>>
>> $ netperf -H 10.39.16.7 -l 30 -t TCP_STREAM
>> MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
>> 10.39.16.7 () port 0 AF_INET : demo
>> Recv Send Send
>> Socket Socket Message Elapsed
>> Size Size Size Time Throughput
>> bytes bytes bytes secs. 10^6bits/sec
>>
>> 87380 16384 16384 30.00 9386.73
>>
>>
>> With XDP
>>
>> $ netperf -H 10.39.16.7 -l 30 -t TCP_STREAM
>> MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
>> 10.39.16.7 () port 0 AF_INET : demo
>> Recv Send Send
>> Socket Socket Message Elapsed
>> Size Size Size Time Throughput
>> bytes bytes bytes secs. 10^6bits/sec
>>
>> 87380 16384 16384 30.01 384.11
>>
>>
>> Prior versions was showing throughput of at least 4000 (depends on the
>> test and VM setup).
>
> Thanks for testing this. And a good thing we have counters for this.
> Are the rx_xdp_drops or rx_xdp_bad_drops non-zero/increasing?
>
Patches are now in the kernel. Tests Friday and yesterday were showing a
lot of variability, so may be an issue with the servers / lab setup I am
using. I need to follow up on that.
prev parent reply other threads:[~2019-11-03 17:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 10:21 [PATCH net-next v4 0/6] sfc: Add XDP support Charles McLachlan
2019-10-31 10:23 ` [PATCH net-next v4 1/6] sfc: support encapsulation of xdp_frames in efx_tx_buffer Charles McLachlan
2019-10-31 19:54 ` Jesper Dangaard Brouer
2019-10-31 10:23 ` [PATCH net-next v4 2/6] sfc: perform XDP processing on received packets Charles McLachlan
2019-10-31 19:59 ` Jesper Dangaard Brouer
2019-10-31 10:23 ` [PATCH net-next v4 3/6] sfc: Enable setting of xdp_prog Charles McLachlan
2019-10-31 20:00 ` Jesper Dangaard Brouer
2019-10-31 10:23 ` [PATCH net-next v4 4/6] sfc: allocate channels for XDP tx queues Charles McLachlan
2019-10-31 20:04 ` Jesper Dangaard Brouer
2019-10-31 10:24 ` [PATCH net-next v4 5/6] sfc: handle XDP_TX outcomes of XDP eBPF programs Charles McLachlan
2019-10-31 20:14 ` Jesper Dangaard Brouer
2019-10-31 10:24 ` [PATCH net-next v4 6/6] sfc: add XDP counters to ethtool stats Charles McLachlan
2019-10-31 20:13 ` Jesper Dangaard Brouer
2019-10-31 20:20 ` David Ahern
2019-10-31 18:42 ` [PATCH net-next v4 0/6] sfc: Add XDP support David Miller
2019-10-31 21:15 ` David Miller
2019-10-31 22:18 ` David Ahern
2019-11-01 10:07 ` Martin Habets
2019-11-03 17:24 ` David Ahern [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=236ff7c4-95da-da0e-8ba7-12bfb92c7d55@gmail.com \
--to=dsahern@gmail.com \
--cc=brouer@redhat.com \
--cc=cmclachlan@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=mhabets@solarflare.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).