From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: netdev@vger.kernel.org, sowmini.varadhan@oracle.com
Cc: daniel@iogearbox.net, willemb@google.com, davem@davemloft.net
Subject: [PATCH v2 net-next 0/2] TPACKET_V3 TX_RING support
Date: Sun, 1 Jan 2017 14:45:13 -0800 [thread overview]
Message-ID: <cover.1483309545.git.sowmini.varadhan@oracle.com> (raw)
This patch series allows an application to use a single PF_PACKET
descriptor and leverage the best implementations of TX_RING
and RX_RING that exist today.
Updates in v2 are listed below:
- patch 1 (which builds on the earlier patch discussed at
http://patchwork.ozlabs.org/patch/709840/) verifies that tp_next_offset
is set to 0 for TPACKET_V3 in the tpacket_snd path, indicating that
variable-sized frames are not in use. Applications that wish to do
block-sends must fill up multiple frames in the Tx ring and then
trigger the transmit. At the current time, only fixed-size frames are
supported on TX_RING for TPACKET_V3.
- patch 2 in this series adds a test case and sample code for
(TPACKET_V3, PACKET_TX_RING) in testing/selftests
Sowmini Varadhan (2):
af_packet: TX_RING support for TPACKET_V3
tools: test case for TPACKET_V3/TX_RING support
Documentation/networking/packet_mmap.txt | 9 ++-
net/packet/af_packet.c | 27 +++++--
tools/testing/selftests/net/psock_tpacket.c | 110 ++++++++++++++++++++++++++-
3 files changed, 135 insertions(+), 11 deletions(-)
next reply other threads:[~2017-01-01 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 22:45 Sowmini Varadhan [this message]
2017-01-01 22:45 ` [PATCH v2 net-next 1/2] af_packet: TX_RING support for TPACKET_V3 Sowmini Varadhan
2017-01-02 22:57 ` Willem de Bruijn
2017-01-02 23:07 ` Sowmini Varadhan
2017-01-01 22:45 ` [PATCH v2 net-next 2/2] tools: test case for TPACKET_V3/TX_RING support Sowmini Varadhan
2017-01-02 22:31 ` Willem de Bruijn
2017-01-02 23:02 ` Sowmini Varadhan
2017-01-02 23:15 ` Willem de Bruijn
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=cover.1483309545.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.