From: Leon Romanovsky <leon@kernel.org> To: Jakub Kicinski <kuba@kernel.org> Cc: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>, Willem de Bruijn <willemdebruijn.kernel@gmail.com>, Sasha Levin <sashal@kernel.org>, Pavan Kumar Linga <pavan.kumar.linga@intel.com>, willemb@google.com, decot@google.com, netdev@vger.kernel.org, jesse.brandeburg@intel.com, edumazet@google.com, intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com, pabeni@redhat.com, davem@davemloft.net Subject: Re: [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF driver Date: Thu, 13 Apr 2023 10:15:29 +0300 [thread overview] Message-ID: <20230413071529.GE182481@unreal> (raw) In-Reply-To: <20230412192434.53d55c20@kernel.org> On Wed, Apr 12, 2023 at 07:24:34PM -0700, Jakub Kicinski wrote: > On Wed, 12 Apr 2023 19:03:22 -0500 Samudrala, Sridhar wrote: > > On 4/12/2023 2:16 PM, Willem de Bruijn wrote: > > > Sasha Levin wrote: > > >> On Mon, Apr 10, 2023 at 06:13:39PM -0700, Pavan Kumar Linga wrote: > > >> How will this work when the OASIS driver is ready down the road? > > >> > > >> We'll end up with two "idpf" drivers, where one will work with hardware > > >> that is not fully spec compliant using this Intel driver, and everything > > >> else will use the OASIS driver? > > >> > > >> Does Intel plan to remove this driver when the OASIS one lands? > > >> > > >> At the very least, having two "idpf" drivers will be very confusing. > > > > > > One approach is that when the OASIS v1 spec is published, this driver > > > is updated to match that and moved out of the intel directory. > > > > Yes. We don't want to have 2 idpf drivers in the upstream kernel. > > It will be an Intel vendor driver until it becomes a standard. > > Hope it will be OK to move the driver out of the intel directory when > > that happens. > > As I said previously in [0] until there is a compatible, widely > available implementation from a second vendor - this is an Intel > driver and nothing more. It's not moving anywhere. Even if second implementation arrives, it is unlikely that this idpf driver will be moved. Mainly because of different level of review between vendor driver vs. standard one, and expected pushback to any incompatible changes in existing driver as it is already deployed. Thanks > > I think that's a reasonable position which should allow Intel to ship > your code and me to remain professional. > > [0] https://lore.kernel.org/all/20230403163025.5f40a87c@kernel.org/
WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leon@kernel.org> To: Jakub Kicinski <kuba@kernel.org> Cc: Sasha Levin <sashal@kernel.org>, Willem de Bruijn <willemdebruijn.kernel@gmail.com>, pabeni@redhat.com, willemb@google.com, jesse.brandeburg@intel.com, edumazet@google.com, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, anthony.l.nguyen@intel.com, decot@google.com, davem@davemloft.net Subject: Re: [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF driver Date: Thu, 13 Apr 2023 10:15:29 +0300 [thread overview] Message-ID: <20230413071529.GE182481@unreal> (raw) In-Reply-To: <20230412192434.53d55c20@kernel.org> On Wed, Apr 12, 2023 at 07:24:34PM -0700, Jakub Kicinski wrote: > On Wed, 12 Apr 2023 19:03:22 -0500 Samudrala, Sridhar wrote: > > On 4/12/2023 2:16 PM, Willem de Bruijn wrote: > > > Sasha Levin wrote: > > >> On Mon, Apr 10, 2023 at 06:13:39PM -0700, Pavan Kumar Linga wrote: > > >> How will this work when the OASIS driver is ready down the road? > > >> > > >> We'll end up with two "idpf" drivers, where one will work with hardware > > >> that is not fully spec compliant using this Intel driver, and everything > > >> else will use the OASIS driver? > > >> > > >> Does Intel plan to remove this driver when the OASIS one lands? > > >> > > >> At the very least, having two "idpf" drivers will be very confusing. > > > > > > One approach is that when the OASIS v1 spec is published, this driver > > > is updated to match that and moved out of the intel directory. > > > > Yes. We don't want to have 2 idpf drivers in the upstream kernel. > > It will be an Intel vendor driver until it becomes a standard. > > Hope it will be OK to move the driver out of the intel directory when > > that happens. > > As I said previously in [0] until there is a compatible, widely > available implementation from a second vendor - this is an Intel > driver and nothing more. It's not moving anywhere. Even if second implementation arrives, it is unlikely that this idpf driver will be moved. Mainly because of different level of review between vendor driver vs. standard one, and expected pushback to any incompatible changes in existing driver as it is already deployed. Thanks > > I think that's a reasonable position which should allow Intel to ship > your code and me to remain professional. > > [0] https://lore.kernel.org/all/20230403163025.5f40a87c@kernel.org/ _______________________________________________ Intel-wired-lan mailing list Intel-wired-lan@osuosl.org https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-04-13 7:15 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 1:13 [PATCH net-next v2 00/15] Introduce Intel IDPF driver Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 1:13 ` [PATCH net-next v2 01/15] virtchnl: add virtchnl version 2 ops Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 8:51 ` Simon Horman 2023-04-11 8:51 ` [Intel-wired-lan] " Simon Horman 2023-04-12 21:38 ` Tantilov, Emil S 2023-04-12 21:38 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-11 1:13 ` [PATCH net-next v2 02/15] idpf: add module register and probe functionality Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 12:36 ` Leon Romanovsky 2023-04-11 12:36 ` [Intel-wired-lan] " Leon Romanovsky 2023-04-12 23:10 ` Tantilov, Emil S 2023-04-12 23:10 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-13 6:03 ` Leon Romanovsky 2023-04-13 6:03 ` [Intel-wired-lan] " Leon Romanovsky 2023-04-13 18:58 ` Tantilov, Emil S 2023-04-13 18:58 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-20 18:13 ` Tantilov, Emil S 2023-04-20 18:13 ` Tantilov, Emil S 2023-04-20 18:20 ` Leon Romanovsky 2023-04-20 18:20 ` Leon Romanovsky 2023-04-11 1:13 ` [PATCH net-next v2 03/15] idpf: add controlq init and reset checks Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 9:19 ` Simon Horman 2023-04-11 9:19 ` [Intel-wired-lan] " Simon Horman 2023-04-11 1:13 ` [PATCH net-next v2 04/15] idpf: add core init and interrupt request Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 9:52 ` Simon Horman 2023-04-11 9:52 ` [Intel-wired-lan] " Simon Horman 2023-04-13 19:10 ` Tantilov, Emil S 2023-04-13 19:10 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-11 1:13 ` [PATCH net-next v2 05/15] idpf: add create vport and netdev configuration Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 06/15] idpf: continue expanding init task Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 9:04 ` [Intel-wired-lan] " Simon Horman 2023-04-11 9:04 ` Simon Horman 2023-04-13 19:04 ` Tantilov, Emil S 2023-04-13 19:04 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-11 1:13 ` [PATCH net-next v2 07/15] idpf: configure resources for TX queues Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 08/15] idpf: configure resources for RX queues Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 09/15] idpf: initialize interrupts and enable vport Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 10/15] idpf: add splitq start_xmit Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 1:13 ` [PATCH net-next v2 11/15] idpf: add TX splitq napi poll support Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] " Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 12/15] idpf: add RX " Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 13/15] idpf: add singleq start_xmit and napi poll Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 14/15] idpf: add ethtool callbacks Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-11 9:55 ` Simon Horman 2023-04-11 9:55 ` [Intel-wired-lan] " Simon Horman 2023-04-13 19:11 ` Tantilov, Emil S 2023-04-13 19:11 ` [Intel-wired-lan] " Tantilov, Emil S 2023-04-22 5:26 ` Tantilov, Emil S 2023-04-22 5:26 ` Tantilov, Emil S 2023-04-22 7:55 ` Simon Horman 2023-04-22 7:55 ` Simon Horman 2023-04-11 1:13 ` [Intel-wired-lan] [PATCH net-next v2 15/15] idpf: configure SRIOV and add other ndo_ops Pavan Kumar Linga 2023-04-11 1:13 ` Pavan Kumar Linga 2023-04-12 18:25 ` [Intel-wired-lan] [PATCH net-next v2 00/15] Introduce Intel IDPF driver Sasha Levin 2023-04-12 18:25 ` Sasha Levin 2023-04-12 19:16 ` Willem de Bruijn 2023-04-12 19:16 ` Willem de Bruijn 2023-04-13 0:03 ` Samudrala, Sridhar 2023-04-13 0:03 ` Samudrala, Sridhar 2023-04-13 2:24 ` Jakub Kicinski 2023-04-13 2:24 ` Jakub Kicinski 2023-04-13 7:15 ` Leon Romanovsky [this message] 2023-04-13 7:15 ` Leon Romanovsky 2023-04-14 22:01 ` Sasha Levin 2023-04-14 22:01 ` Sasha Levin 2023-04-14 22:27 ` Jakub Kicinski 2023-04-14 22:27 ` Jakub Kicinski 2023-04-15 17:16 ` Sasha Levin 2023-04-15 17:16 ` Sasha Levin 2023-04-17 16:38 ` Jakub Kicinski 2023-04-17 16:38 ` Jakub Kicinski
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=20230413071529.GE182481@unreal \ --to=leon@kernel.org \ --cc=anthony.l.nguyen@intel.com \ --cc=davem@davemloft.net \ --cc=decot@google.com \ --cc=edumazet@google.com \ --cc=intel-wired-lan@lists.osuosl.org \ --cc=jesse.brandeburg@intel.com \ --cc=kuba@kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pabeni@redhat.com \ --cc=pavan.kumar.linga@intel.com \ --cc=sashal@kernel.org \ --cc=sridhar.samudrala@intel.com \ --cc=willemb@google.com \ --cc=willemdebruijn.kernel@gmail.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: linkBe 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.