From: Jakub Kicinski <kuba@kernel.org>
To: "Nambiar, Amritha" <amritha.nambiar@intel.com>
Cc: <netdev@vger.kernel.org>, <sridhar.samudrala@intel.com>
Subject: Re: [net-next PATCH v4 04/10] netdev-genl: Add netlink framework functions for queue
Date: Thu, 12 Oct 2023 17:36:36 -0700 [thread overview]
Message-ID: <20231012173636.68e6eeee@kernel.org> (raw)
In-Reply-To: <8c9704c0-532e-4d35-a073-bee771cd78c5@intel.com>
On Thu, 12 Oct 2023 17:24:41 -0700 Nambiar, Amritha wrote:
> I was thinking your review comment was for the entire
> 'netdev_nl_queue_validate' function (i.e. if the max queue-id validation
> can be handled in the policy as a range with max value for queue-id, and
> since max queue-id was not a constant, but varies within the kernel, ex:
> netdev->real_num_rx_queues, I was unsure of it...). So, another option I
> could come up with for the validation was a 'pre_doit' hook instead of
> netdev_nl_queue_validate().
real_num can change if we're not holding rtnl_lock, and we can't hold
the lock in pre :(
> If your comment referred to the enum queue-type range alone, I see,
> since the policy handles the max check for queue-type, I can remove the
> default case returning EOPNOTSUPP. Correct me if I'm wrong.
Yup! I only meant the type, you can trust netlink to validate the type.
next prev parent reply other threads:[~2023-10-13 0:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 9:14 [net-next PATCH v4 00/10] Introduce queue and NAPI support in netdev-genl (Was: Introduce NAPI queues support) Amritha Nambiar
2023-10-06 9:14 ` [net-next PATCH v4 01/10] netdev-genl: spec: Extend netdev netlink spec in YAML for queue Amritha Nambiar
2023-10-11 2:12 ` Jakub Kicinski
2023-10-11 23:28 ` Nambiar, Amritha
2023-10-06 9:14 ` [net-next PATCH v4 02/10] net: Add queue and napi association Amritha Nambiar
2023-10-11 2:17 ` Jakub Kicinski
2023-10-11 23:36 ` Nambiar, Amritha
2023-10-06 9:14 ` [net-next PATCH v4 03/10] ice: Add support in the driver for associating queue with napi Amritha Nambiar
2023-10-06 9:14 ` [net-next PATCH v4 04/10] netdev-genl: Add netlink framework functions for queue Amritha Nambiar
2023-10-11 2:25 ` Jakub Kicinski
2023-10-11 23:54 ` Nambiar, Amritha
2023-10-12 23:48 ` Jakub Kicinski
2023-10-13 0:24 ` Nambiar, Amritha
2023-10-13 0:36 ` Jakub Kicinski [this message]
2023-10-13 0:40 ` Nambiar, Amritha
2023-10-13 0:44 ` Jakub Kicinski
2023-10-06 9:15 ` [net-next PATCH v4 05/10] netdev-genl: spec: Extend netdev netlink spec in YAML for NAPI Amritha Nambiar
2023-10-06 9:15 ` [net-next PATCH v4 06/10] netdev-genl: Add netlink framework functions for napi Amritha Nambiar
2023-10-11 2:29 ` Jakub Kicinski
2023-10-11 23:55 ` Nambiar, Amritha
2023-10-06 9:15 ` [net-next PATCH v4 07/10] netdev-genl: spec: Add irq in netdev netlink YAML spec Amritha Nambiar
2023-10-06 9:15 ` [net-next PATCH v4 08/10] net: Add NAPI IRQ support Amritha Nambiar
2023-10-06 9:15 ` [net-next PATCH v4 09/10] netdev-genl: spec: Add PID in netdev netlink YAML spec Amritha Nambiar
2023-10-06 9:15 ` [net-next PATCH v4 10/10] netdev-genl: Add PID for the NAPI thread Amritha Nambiar
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=20231012173636.68e6eeee@kernel.org \
--to=kuba@kernel.org \
--cc=amritha.nambiar@intel.com \
--cc=netdev@vger.kernel.org \
--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).