From: Jesper Dangaard Brouer <brouer@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v4 2/6] igb: take vlan double header into account
Date: Tue, 1 Dec 2020 09:58:52 +0100 [thread overview]
Message-ID: <20201201095852.2dc1e8f8@carbon> (raw)
In-Reply-To: <DM6PR11MB454615FDFC4E7B71D9B82FA29CF40@DM6PR11MB4546.namprd11.prod.outlook.com>
On Tue, 1 Dec 2020 08:23:23 +0000
"Penigalapati, Sandeep" <sandeep.penigalapati@intel.com> wrote:
> Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
Very happy that you are testing this.
Have you also tested that samples/bpf/ xdp_redirect_cpu program works?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Penigalapati, Sandeep" <sandeep.penigalapati@intel.com>
Cc: "sven.auhagen@voleatech.de" <sven.auhagen@voleatech.de>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
"pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>,
brouer@redhat.com
Subject: Re: [PATCH v4 2/6] igb: take vlan double header into account
Date: Tue, 1 Dec 2020 09:58:52 +0100 [thread overview]
Message-ID: <20201201095852.2dc1e8f8@carbon> (raw)
In-Reply-To: <DM6PR11MB454615FDFC4E7B71D9B82FA29CF40@DM6PR11MB4546.namprd11.prod.outlook.com>
On Tue, 1 Dec 2020 08:23:23 +0000
"Penigalapati, Sandeep" <sandeep.penigalapati@intel.com> wrote:
> Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
Very happy that you are testing this.
Have you also tested that samples/bpf/ xdp_redirect_cpu program works?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2020-12-01 8:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:04 [Intel-wired-lan] [PATCH v4 0/6] igb: xdp patches followup sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 1/6] igb: XDP xmit back fix error code sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-12-08 12:47 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-12-08 12:47 ` Penigalapati, Sandeep
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 2/6] igb: take vlan double header into account sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-12-01 8:23 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-12-01 8:23 ` Penigalapati, Sandeep
2020-12-01 8:58 ` Jesper Dangaard Brouer [this message]
2020-12-01 8:58 ` Jesper Dangaard Brouer
2020-12-05 9:42 ` [Intel-wired-lan] " Sven Auhagen
2020-12-05 9:42 ` Sven Auhagen
2020-12-08 10:52 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-12-08 10:52 ` Penigalapati, Sandeep
2020-12-08 11:39 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2020-12-08 11:39 ` Jesper Dangaard Brouer
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 3/6] igb: XDP extack message on error sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 4/6] igb: skb add metasize for xdp sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-12-08 12:50 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-12-08 12:50 ` Penigalapati, Sandeep
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 5/6] igb: use xdp_do_flush sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-12-01 7:30 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-12-01 7:30 ` Penigalapati, Sandeep
2020-11-11 17:04 ` [Intel-wired-lan] [PATCH v4 6/6] igb: avoid transmit queue timeout in xdp path sven.auhagen
2020-11-11 17:04 ` sven.auhagen
2020-11-24 14:49 ` [Intel-wired-lan] " Penigalapati, Sandeep
2020-11-24 14:49 ` Penigalapati, Sandeep
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=20201201095852.2dc1e8f8@carbon \
--to=brouer@redhat.com \
--cc=intel-wired-lan@osuosl.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 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.