DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"techboard@dpdk.org" <techboard@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK techboard minutes @18/12/2019
Date: Tue, 24 Dec 2019 11:34:32 +0000	[thread overview]
Message-ID: <25d91d5a4ec88e166818419a8a1ec67006839a96.camel@debian.org> (raw)
In-Reply-To: <SN6PR11MB2558D2A5264A6D287247155D9A2D0@SN6PR11MB2558.namprd11.prod.outlook.com>

On Fri, 2019-12-20 at 16:33 +0000, Ananyev, Konstantin wrote:
> Minutes of Technical Board Meeting, 2019-12-18
> 
> Members Attending
> -----------------
> -Bruce
> -Ferruh
> -Hemant
> -Honnappa
> -Jerin
> -Kevin  
> -Konstantin (Chair)
> -Maxime
> -Olivier
> -Stephen
> -Thomas
> 
> NOTE: The technical board meetings every second Wednesday on IRC
> channel  #dpdk-board, at 3pm UTC. Meetings are public and DPDK
> community
> members are welcome to attend.
> 
> NOTE: Next meeting will be on Wednesday 2020-01-15 @3pm UTC, and will
> be
> chaired by Maxime Coquelin
> 
> 1) drivers/vdpa introduction discussion.
> Currently, at dpdk.org we have only IFC vDPA driver available
> (located in drivers/net),
> but more drivers are arriving (Mellanox, Virtio vDPA in v20.02).
> Might be some others are expected in later releases.
> Mellanox proposal is to introduce a new vDPA subsystem
> (drivers/vdpa),
> and move code common to both net and vdpa PMDs to the drivers/common
> directory.
> drivers/net/ifc will be moved entirely into drivers/vdpa/ifc
> While it seems to provide better code layout for drivers in long run,
> in short term it probably would need significant code refactoring for
> both mlx and virtio PMDs,
> plus can cause some difficulties for stable release maintainers.
> 
> AR to Maxime (virtio) and Matan (mlx) to estimate how big code
> refactoring will be required for such move.
> AR to stable release maintainers (Kevin and Luca) to estimate impact
> on stable releases.
> Decision at next TB meeting based on provided estimations/feedback.

Hi,

At a glance, the impact will be more time consuming backports, as fewer
patches will "cleanly" backport and require manual work, which will
lead to fewer patches being integrated directly by ourselves. Are the
PMDs devs/maintainers willing/available to do extra work to help
backporting fixes?

-- 
Kind regards,
Luca Boccassi

      parent reply	other threads:[~2019-12-24 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 16:33 Ananyev, Konstantin
2019-12-22 16:15 ` Matan Azrad
2019-12-24 11:34 ` Luca Boccassi [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=25d91d5a4ec88e166818419a8a1ec67006839a96.camel@debian.org \
    --to=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=techboard@dpdk.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).