DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Tudor Cornea <tudor.cornea@gmail.com>
Cc: <linville@tuxdriver.com>, <andrew.rybchenko@oktetlabs.ru>,
	<thomas@monjalon.net>, <jerinj@marvell.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] net/af_packet: reinsert the stripped vlan tag
Date: Wed, 6 Oct 2021 10:42:14 +0100	[thread overview]
Message-ID: <ffe67cd4-1c59-af82-0644-2b870b2344d7@intel.com> (raw)
In-Reply-To: <20211001080225.442806c4@hermes.local>

On 10/1/2021 4:02 PM, Stephen Hemminger wrote:
> On Fri,  1 Oct 2021 11:35:01 +0300
> Tudor Cornea <tudor.cornea@gmail.com> wrote:
> 
>> The af_packet pmd driver binds to a raw socket and allows
>> sending and receiving of packets through the kernel.
>>
>> Since commit [1], the kernel strips the vlan tags early in
>> __netif_receive_skb_core(), so we receive untagged packets while
>> running with the af_packet pmd.
>>
>> Luckily for us, the skb vlan-related fields are still populated from the
>> stripped vlan tags, so we end up having all the information
>> that we need in the mbuf.
>>
>> Having the pmd driver support DEV_RX_OFFLOAD_VLAN_STRIP allows the
>> application to control the desired vlan stripping behavior,
>> until we have a way to describe offloads that can't be disabled by
>> pmd drivers.
>>
>> This patch will cause a change in the default way that the af_packet
>> pmd treats received vlan-tagged frames. While previously, the
>> application was required to check the PKT_RX_VLAN_STRIPPED flag, after
>> this patch, the pmd will re-insert the vlan tag transparently to the
>> user, unless the DEV_RX_OFFLOAD_VLAN_STRIP is enabled in
>> rxmode.offloads.
>>
>> I've attempted a preliminary benchmark to understand if the change could
>> cause a sizable performance hit.
>>
>> Setup:
>> Two virtual machines running on top of an ESXi hypervisor
>>
>> Tx: DPDK app (running on top of vmxnet3 PMD)
>> Rx: af_packet (running on top of a kernel vmxnet3 interface)
>> Packet size :68 (packet contains a vlan tag)
>>
>> Rates:
>> Tx - 1.419 Mpps
>> Rx (without vlan insertion) - 1227636 pps
>> Rx (with vlan insertion)    - 1220081 pps
>>
>> At a first glance, we don't seem to have a large degradation in terms
>> of packet rate.
>>
>> [1] https://github.com/torvalds/linux/commit/bcc6d47903612c3861201cc3a866fb604f26b8b2
>>
>> Signed-off-by: Tudor Cornea <tudor.cornea@gmail.com>
> 
> 
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> 

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/main, thanks.
Release notes slightly updated, to simplify the sentences, while merging.

      reply	other threads:[~2021-10-06  9:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 12:46 [dpdk-dev] [PATCH] net/af_packet: try to " Tudor Cornea
2021-08-31 15:31 ` Ferruh Yigit
2021-09-01 19:07   ` Tudor Cornea
2021-09-01 21:34     ` Stephen Hemminger
2021-09-02 10:49       ` Ferruh Yigit
2021-09-03  9:45         ` Tudor Cornea
2021-09-08  8:59 ` [dpdk-dev] [PATCH v2] net/af_packet: " Tudor Cornea
2021-09-20 15:40   ` Ferruh Yigit
2021-09-21 20:59     ` Tudor Cornea
2021-09-24 11:44   ` [dpdk-dev] [PATCH v3] " Tudor Cornea
2021-09-24 15:10     ` Stephen Hemminger
2021-09-29 14:13       ` Tudor Cornea
2021-09-29 14:08     ` [dpdk-dev] [PATCH v4] " Tudor Cornea
2021-09-30  8:14       ` Ferruh Yigit
2021-10-01  8:49         ` Tudor Cornea
2021-10-01  8:35       ` [dpdk-dev] [PATCH v5] " Tudor Cornea
2021-10-01 15:02         ` Stephen Hemminger
2021-10-06  9:42           ` Ferruh Yigit [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=ffe67cd4-1c59-af82-0644-2b870b2344d7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=linville@tuxdriver.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=tudor.cornea@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).