Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1 0/7] udp_tunnel: convert Intel drivers with shared tables
Date: Thu, 23 Jul 2020 20:06:15 +0000	[thread overview]
Message-ID: <bfa03cf8613ada508774a2e6e89b9b01bfd968dd.camel@intel.com> (raw)
In-Reply-To: <1af4aea7869bdb9f3991536b6449521b214ed103.camel@intel.com>

On Wed, 2020-07-22 at 14:22 -0700, Tony Nguyen wrote:
> On Tue, 2020-07-21 at 18:27 -0700, Jakub Kicinski wrote:
> > This set converts Intel drivers which have the ability to spawn
> > multiple netdevs, but have only one UDP tunnel port table.
> > 
> > Appropriate support is added to the core infra in patch 1,
> > followed by netdevsim support and a selftest.
> > 
> > The table sharing works by core attaching the same table
> > structure to all devices sharing the table. This means the
> > reference count has to accommodate potentially large values.
> > 
> > Once core is ready i40e and ice are converted. These are
> > complex drivers, and I don't have HW to test so please
> > review..
> 
> I'm requesting our developers to take a look over and validation to
> test the ice and i40e patches. I will report back when I get results.

Would you mind if I pick these patches up into Jeff's tree? It will
make it easier to test that way.

Thanks,
Tony

  reply	other threads:[~2020-07-23 20:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  1:27 [Intel-wired-lan] [PATCH net-next v1 0/7] udp_tunnel: convert Intel drivers with shared tables Jakub Kicinski
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 1/7] udp_tunnel: add the ability to share port tables Jakub Kicinski
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 2/7] netdevsim: add warnings on unexpected UDP tunnel port errors Jakub Kicinski
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 3/7] netdevsim: shared UDP tunnel port table support Jakub Kicinski
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 4/7] selftests: net: add a test for shared UDP tunnel info tables Jakub Kicinski
2020-09-19  7:23   ` Brown, Aaron F
2020-09-21 21:44     ` Jakub Kicinski
2020-09-22 17:34       ` Brown, Aaron F
2020-09-22 18:35         ` Jakub Kicinski
2020-09-24 22:25       ` Nguyen, Anthony L
2020-09-24 22:28         ` Jakub Kicinski
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 5/7] i40e: convert to new udp_tunnel infrastructure Jakub Kicinski
2020-09-19  7:04   ` Brown, Aaron F
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 6/7] ice: remove unused args from ice_get_open_tunnel_port() Jakub Kicinski
2020-09-19  5:40   ` Brown, Aaron F
2020-07-22  1:27 ` [Intel-wired-lan] [PATCH net-next v1 7/7] ice: convert to new udp_tunnel infrastructure Jakub Kicinski
2020-09-19  5:42   ` Brown, Aaron F
2020-07-22 21:22 ` [Intel-wired-lan] [PATCH net-next v1 0/7] udp_tunnel: convert Intel drivers with shared tables Nguyen, Anthony L
2020-07-23 20:06   ` Nguyen, Anthony L [this message]
2020-07-23 20:17     ` David Miller
2020-09-03 23:22     ` Jakub Kicinski
2020-09-04 16:12       ` Nguyen, Anthony L

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=bfa03cf8613ada508774a2e6e89b9b01bfd968dd.camel@intel.com \
    --to=anthony.l.nguyen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox