public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel•com>
To: Jakub Kicinski <kuba@kernel•org>
Cc: <davem@davemloft•net>, <pabeni@redhat•com>, <edumazet@google•com>,
	<netdev@vger•kernel.org>, <michal.swiatkowski@linux•intel.com>
Subject: Re: [PATCH net-next 00/15][pull request] ice: support devlink subfunction
Date: Wed, 31 Jul 2024 08:45:11 -0700	[thread overview]
Message-ID: <086058b6-0dd8-e61e-e905-1647ed62dc00@intel.com> (raw)
In-Reply-To: <20240730184544.60ff163c@kernel.org>



On 7/30/2024 6:45 PM, Jakub Kicinski wrote:
> On Mon, 29 Jul 2024 15:34:15 -0700 Tony Nguyen wrote:
>> Currently ice driver does not allow creating more than one networking
>> device per physical function. The only way to have more hardware backed
>> netdev is to use SR-IOV.
>>
>> Following patchset adds support for devlink port API. For each new
>> pcisf type port, driver allocates new VSI, configures all resources
>> needed, including dynamically MSIX vectors, program rules and registers
>> new netdev.
>>
>> This series supports only one Tx/Rx queue pair per subfunction.
> 
> I'm a bit surprised not to see Jiri on the CC list here, didn't
> he provide feedback on this series in the past?.. Yes he did.
> 
> Please repost and CC everyone who gave you feedback.

Will do.

Thanks,
Tony

      reply	other threads:[~2024-07-31 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 22:34 [PATCH net-next 00/15][pull request] ice: support devlink subfunction Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 01/15] ice: add new VSI type for subfunctions Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 02/15] ice: export ice ndo_ops functions Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 03/15] ice: add basic devlink subfunctions support Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 04/15] ice: treat subfunction VSI the same as PF VSI Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 05/15] ice: allocate devlink for subfunction Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 06/15] ice: base subfunction aux driver Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 07/15] ice: implement netdev for subfunction Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 08/15] ice: make representor code generic Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 09/15] ice: create port representor for SF Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 10/15] ice: don't set target VSI for subfunction Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 11/15] ice: check if SF is ready in ethtool ops Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 12/15] ice: implement netdevice ops for SF representor Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 13/15] ice: support subfunction devlink Tx topology Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 14/15] ice: basic support for VLAN in subfunctions Tony Nguyen
2024-07-29 22:34 ` [PATCH net-next 15/15] ice: allow to activate and deactivate subfunction Tony Nguyen
2024-07-31  1:45 ` [PATCH net-next 00/15][pull request] ice: support devlink subfunction Jakub Kicinski
2024-07-31 15:45   ` Tony Nguyen [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=086058b6-0dd8-e61e-e905-1647ed62dc00@intel.com \
    --to=anthony.l.nguyen@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=michal.swiatkowski@linux$(echo .)intel.com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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