From: "Björn Töpel" <bjorn.topel@intel.com>
To: "Jesper Dangaard Brouer" <brouer@redhat.com>,
"Björn Töpel" <bjorn.topel@gmail.com>
Cc: jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
magnus.karlsson@intel.com, magnus.karlsson@gmail.com,
ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
u9012063@gmail.com, tuc@vmware.com, jakub.kicinski@netronome.com
Subject: Re: [PATCH v2 0/5] Introducing ixgbe AF_XDP ZC support
Date: Fri, 5 Oct 2018 06:59:52 +0200 [thread overview]
Message-ID: <5a801d72-6dcd-a8e4-f1a6-c8f3cc1e560e@intel.com> (raw)
In-Reply-To: <20181004231848.33efd81f@redhat.com>
On 2018-10-04 23:18, Jesper Dangaard Brouer wrote:
> I see similar performance numbers, but my system can crash with 'txonly'.
Thanks for finding this, Jesper!
Can you give me your "lspci -vvv" dump of your NIC, so I know what ixgbe
flavor you've got?
I'll dig into it right away.
Björn
next prev parent reply other threads:[~2018-10-05 11:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 8:00 [PATCH v2 0/5] Introducing ixgbe AF_XDP ZC support Björn Töpel
2018-10-02 8:00 ` [PATCH v2 1/5] ixgbe: added Rx/Tx ring disable/enable functions Björn Töpel
2018-10-02 18:25 ` William Tu
2018-10-02 8:00 ` [PATCH v2 2/5] ixgbe: move common Rx functions to ixgbe_txrx_common.h Björn Töpel
2018-10-02 18:27 ` William Tu
2018-10-02 8:00 ` [PATCH v2 3/5] ixgbe: add AF_XDP zero-copy Rx support Björn Töpel
2018-10-02 18:26 ` William Tu
2018-10-02 8:00 ` [PATCH v2 4/5] ixgbe: move common Tx functions to ixgbe_txrx_common.h Björn Töpel
2018-10-02 18:28 ` William Tu
2018-10-02 8:00 ` [PATCH v2 5/5] ixgbe: add AF_XDP zero-copy Tx support Björn Töpel
2018-10-02 18:26 ` William Tu
2018-10-02 18:23 ` [PATCH v2 0/5] Introducing ixgbe AF_XDP ZC support William Tu
2018-10-02 18:39 ` Björn Töpel
2018-10-02 18:43 ` William Tu
2018-10-04 21:18 ` Jesper Dangaard Brouer
2018-10-05 4:59 ` Björn Töpel [this message]
2018-10-05 11:30 ` Björn Töpel
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=5a801d72-6dcd-a8e4-f1a6-c8f3cc1e560e@intel.com \
--to=bjorn.topel@intel.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakub.kicinski@netronome.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tuc@vmware.com \
--cc=u9012063@gmail.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).