DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Daly, Jeff" <jeffd@silicom-usa.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Wang, Haiyue" <haiyue.wang@intel.com>,
	ferruh.yigit@amd.com, andrew.rybchenko@oktetlabs.ru,
	bruce.richardson@intel.com
Subject: Re: [PATCH v2] ixgbe/base: Manual AN-37 for troublesome link partners for X550 SFI
Date: Tue, 24 May 2022 12:42:38 +0200	[thread overview]
Message-ID: <11811318.eQLIkvUDd3@thomas> (raw)
In-Reply-To: <DM4PR11MB599498DB9F8AD1122DB9CC47D7D19@DM4PR11MB5994.namprd11.prod.outlook.com>

18/05/2022 02:03, Zhang, Qi Z:
> From: Jeff Daly <jeffd@silicom-usa.com>
> > 
> > Some SFP link partners exhibit a disinclination to autonegotiate with X550
> > configured in SFI mode.  This patch enables a manual AN-37 restart to work
> > around the problem.
> 
> This fix for some specific hardware in base code,
> unfortunately  Intel DPDK team don't have the device
> and the knowledge to approve this,

That's why the work is collaborative.
You should get and trust knowledge from partners.
The only concerns of a maintainer should be:
	- good feature design
	- good code quality
	- no regression in known cases

> the base code is delivered by our kernel software team,
> I will suggest you can send this to the kernel community
> to get the right expert to review.

Which kind of expert do you imagine to review?
Intel team or Silicom people who are pushing these improvements?

There is another problem with asking Linux kernel change first:
the patch will land in GPL code, bringing difficulties to move
in BSD-licensed base code.

I suggest we make this process more flexible:
	1/ a contributor sends a patch for DPDK base code
	   with an explicit grant for backporting in any license.
	2/ Intel checks that there is no DPDK regression
	3/ patch is merged in DPDK
	4/ Intel merges it in the internal base code
	5/ Linux kernel team can backport the fix to Linux
	6/ Any other OS can backport the fix in its driver

Let's make the DPDK process open for everybody.



  reply	other threads:[~2022-05-24 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:15 [PATCH] " Jeff Daly
2022-03-16 18:59 ` [PATCH v2] " Jeff Daly
2022-05-18  0:03   ` Zhang, Qi Z
2022-05-24 10:42     ` Thomas Monjalon [this message]
2022-05-24 13:42       ` Zhang, Qi Z
2022-05-24 15:54         ` Thomas Monjalon
2022-05-25  0:11           ` Zhang, Qi Z
2022-05-25  7:55             ` Thomas Monjalon
2022-05-25  8:29               ` Zhang, Qi Z

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=11811318.eQLIkvUDd3@thomas \
    --to=thomas@monjalon.net \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=haiyue.wang@intel.com \
    --cc=jeffd@silicom-usa.com \
    --cc=qi.z.zhang@intel.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).