DPDK patches and discussions
 help / color / mirror / Atom feed
From: Madhuker Mythri <madhuker.mythri@oracle.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [External] : Re: [PATCH] net/tap: Modified TAP BPF program as per the new Kernel-version upgrade requirements.
Date: Fri, 5 Jan 2024 15:11:22 +0000	[thread overview]
Message-ID: <SJ0PR10MB4798716CDAE44555EA18B7BF97662@SJ0PR10MB4798.namprd10.prod.outlook.com> (raw)
In-Reply-To: <20240104124115.6e6806eb@hermes.local>

By using this " bpf_skb_load_bytes_relative()" helper function we can directly retrieve the Network header data fields, so we no need to check for L2-header VLAN presence.

Thanks,
Madhuker.

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 05 January 2024 02:11
To: Madhuker Mythri <madhuker.mythri@oracle.com>
Cc: ferruh.yigit@amd.com; dev@dpdk.org
Subject: [External] : Re: [PATCH] net/tap: Modified TAP BPF program as per the new Kernel-version upgrade requirements.

On Thu,  4 Jan 2024 22:57:56 +0530
madhuker.mythri@oracle.com wrote:

> -	/* Get correct proto for 802.1ad */
> -	if (skb->vlan_present && skb->vlan_proto == htons(ETH_P_8021AD)) {
> -		if (data + ETH_ALEN * 2 + sizeof(struct vlan_hdr) +
> -		    sizeof(proto) > data_end)
> -			return TC_ACT_OK;
> -		proto = *(__u16 *)(data + ETH_ALEN * 2 +
> -				   sizeof(struct vlan_hdr));
> -		off += sizeof(struct vlan_hdr);
> -	}

Your version loses VLAN support?

  reply	other threads:[~2024-01-05 15:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 17:27 madhuker.mythri
2024-01-04 20:32 ` Stephen Hemminger
2024-01-05 14:58   ` [External] : " Madhuker Mythri
2024-01-04 20:33 ` Stephen Hemminger
2024-01-04 20:35 ` Stephen Hemminger
2024-01-04 20:38 ` Stephen Hemminger
2024-01-05 14:58   ` [External] : " Madhuker Mythri
2024-01-05 17:40     ` Stephen Hemminger
2024-01-04 20:39 ` Stephen Hemminger
2024-01-04 20:41 ` Stephen Hemminger
2024-01-05 15:11   ` Madhuker Mythri [this message]
2024-01-05 17:41     ` [External] : " Stephen Hemminger
2024-01-04 20:42 ` Stephen Hemminger
2024-01-04 20:57 ` Stephen Hemminger
2024-01-05 14:44   ` [External] : " Madhuker Mythri
2024-01-05 17:39     ` Stephen Hemminger
2024-01-06  5:47       ` Madhuker Mythri
2024-01-05 19:30 ` Stephen Hemminger
2024-01-06  5:36   ` [External] : " Madhuker Mythri
2024-01-06 10:23     ` Madhuker Mythri
2024-01-06 16:54       ` Stephen Hemminger
2024-01-06 18:16       ` Stephen Hemminger

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=SJ0PR10MB4798716CDAE44555EA18B7BF97662@SJ0PR10MB4798.namprd10.prod.outlook.com \
    --to=madhuker.mythri@oracle.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=stephen@networkplumber.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).