From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Daly, Jeff" <jeffd@silicom-usa.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>
Subject: RE: [PATCH] net/ixgbe: Treat 1G Cu SFPs as 1G SX on the X550 devices
Date: Tue, 19 Apr 2022 12:32:21 +0000 [thread overview]
Message-ID: <BYAPR11MB3495C64DCCE2F07250E967A9F7F29@BYAPR11MB3495.namprd11.prod.outlook.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D86FDF@smartserver.smartshare.dk>
> -----Original Message-----
> From: Morten Brørup <mb@smartsharesystems.com>
> Sent: Tuesday, April 19, 2022 17:12
> To: Thomas Monjalon <thomas@monjalon.net>; Daly, Jeff <jeffd@silicom-usa.com>; Stephen Hemminger
> <stephen@networkplumber.org>
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Mcnamara,
> John <john.mcnamara@intel.com>
> Subject: RE: [PATCH] net/ixgbe: Treat 1G Cu SFPs as 1G SX on the X550 devices
>
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Thursday, 14 April 2022 19.07
> >
> >
> > > - should print message that when enabled the driver is no longer
> > supported.
> >
> > It could be supported by Silicom.
>
> There's more to "supported by" than meets the eye: When an ODM designs products using Intel chips,
> some sort of customer support from Intel field application engineers is expected by the ODM. We cannot
> expect Silicom to provide design support to anyone but their own customers. E.g. if the NIC is
> behaving weird at the hardware bring-up phase, where it might be any type of problem, Silicom will not
> be able to provide the kind of support required. My point is: There is a difference between community
> support and customer support.
>
> Let me throw up an idea for consideration... I'm trying to think out of the box here, so please
> forgive me if I'm stepping on anyone's toes with this suggestion:
>
> If Intel doesn't want to take on the responsibility and support for this feature graciously donated by
> Silicom (which is obviously Intel's own decision to make), but the DPDK community thinks the feature
> is beneficial, perhaps Silicom could be accepted as the maintainer of this part of the driver? The
> driver would still come with a big fat disclaimer saying that this feature is not supported by Intel,
The first patch author Stephen D has left Silicom:
https://patchwork.dpdk.org/project/dpdk/patch/20211206221922.644187-8-stephend@silicom-usa.com/
How can you expect people can connect to Silicom always ? ; -)
> but maintained by Silicom, who also provides community support for it.
>
> The worst case alternative is a fork or separate add-on patch set offered by the donor. This has
> certainly happened to other projects. Don't get me wrong, we are not there at all regarding this
> feature! I'm just wondering if we can make the DPDK project even more inclusive, so we can avoid forks
> and add-on patch sets now and in the future.
>
> -Morten
next prev parent reply other threads:[~2022-04-19 12:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 22:34 jeffd
2022-04-13 14:21 ` Thomas Monjalon
2022-05-20 0:14 ` Zhang, Qi Z
2022-05-20 18:02 ` Jeff Daly
2022-05-23 5:36 ` Zhang, Qi Z
2022-05-23 14:13 ` Jeff Daly
2022-05-23 23:22 ` Zhang, Qi Z
2022-05-25 15:23 ` Jeff Daly
2022-05-26 0:28 ` Zhang, Qi Z
2022-04-14 1:31 ` Wang, Haiyue
2022-04-14 9:42 ` Thomas Monjalon
2022-04-14 12:13 ` Wang, Haiyue
2022-04-14 12:18 ` Thomas Monjalon
2022-04-14 15:11 ` Jeff Daly
2022-04-14 15:43 ` Stephen Hemminger
2022-04-14 17:06 ` Thomas Monjalon
2022-04-19 9:11 ` Morten Brørup
2022-04-19 12:32 ` Wang, Haiyue [this message]
2022-04-15 1:10 ` Wang, Haiyue
2022-05-26 20:43 ` [PATCH v2] " Jeff Daly
2022-05-29 22:49 ` Zhang, Qi Z
2022-05-30 13:32 ` Jeff Daly
2022-05-30 13:50 ` Zhang, Qi Z
2022-05-31 12:30 ` Jeff Daly
2022-05-31 13:38 ` 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=BYAPR11MB3495C64DCCE2F07250E967A9F7F29@BYAPR11MB3495.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=dev@dpdk.org \
--cc=jeffd@silicom-usa.com \
--cc=john.mcnamara@intel.com \
--cc=mb@smartsharesystems.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).