netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Amritha Nambiar <amritha.nambiar@intel.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, sridhar.samudrala@intel.com
Subject: Re: [net-next PATCH v9 00/11] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support)
Date: Tue, 28 Nov 2023 18:06:09 -0800	[thread overview]
Message-ID: <20231128180609.34a4553e@kernel.org> (raw)
In-Reply-To: <170114286635.10303.8773144948795839629.stgit@anambiarhost.jf.intel.com>

On Mon, 27 Nov 2023 19:49:25 -0800 Amritha Nambiar wrote:
> v8 -> v9
> * Removed locked version __netif_queue_set_napi(), the function
> netif_queue_set_napi() assumes lock is taken. Made changes to ice
> driver to take the lock locally.
> * Detach NAPI from queues by passing NULL to netif_queue_set_napi().
> * Support to avoid listing queue and NAPI info of devices which are
>   DOWN.
> * Includes support for bnxt driver.

The changes since v8 look good.

Please respin because my page pool changes touched netdev.yaml 
in the meantime and this doesn't apply any more.

Please make sure you CC Eric on v10, and Michael on the last patch.
Right now the patchwork get_maintainer check is complaining that
some maintainers were skipped.
-- 
pw-bot: cr

  parent reply	other threads:[~2023-11-29  2:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  3:49 [net-next PATCH v9 00/11] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support) Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 01/11] netdev-genl: spec: Extend netdev netlink spec in YAML for queue Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 02/11] net: Add queue and napi association Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 03/11] ice: Add support in the driver for associating queue with napi Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 04/11] netdev-genl: Add netlink framework functions for queue Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 05/11] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI Amritha Nambiar
2023-11-28  3:49 ` [net-next PATCH v9 06/11] netdev-genl: Add netlink framework functions for napi Amritha Nambiar
2023-11-28  3:50 ` [net-next PATCH v9 07/11] netdev-genl: spec: Add irq in netdev netlink YAML spec Amritha Nambiar
2023-11-28  3:50 ` [net-next PATCH v9 08/11] net: Add NAPI IRQ support Amritha Nambiar
2023-11-28  3:50 ` [net-next PATCH v9 09/11] netdev-genl: spec: Add PID in netdev netlink YAML spec Amritha Nambiar
2023-11-28  3:50 ` [net-next PATCH v9 10/11] netdev-genl: Add PID for the NAPI thread Amritha Nambiar
2023-11-28  3:50 ` [net-next PATCH v9 11/11] eth: bnxt: link NAPI instances to queues and IRQs Amritha Nambiar
2023-11-29  2:06 ` Jakub Kicinski [this message]
2023-11-29 23:51   ` [net-next PATCH v9 00/11] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support) Nambiar, Amritha

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=20231128180609.34a4553e@kernel.org \
    --to=kuba@kernel.org \
    --cc=amritha.nambiar@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sridhar.samudrala@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).