From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org,
sridhar.samudrala@intel.com, jacob.e.keller@intel.com,
pio.raczynski@gmail.com, konrad.knitter@intel.com,
marcin.szycik@intel.com, nex.sw.ncis.nat.hpm.dev@intel.com,
przemyslaw.kitszel@intel.com, jiri@resnulli.us, horms@kernel.org,
David.Laight@aculab.com, pmenzel@molgen.mpg.de,
mschmidt@redhat.com, tatyana.e.nikolova@intel.com,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 0/9][pull request] ice: managing MSI-X in driver
Date: Wed, 5 Feb 2025 06:46:20 +0100 [thread overview]
Message-ID: <Z6L7LPIxHXPz2/ih@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20250204144252.686a466e@kernel.org>
On Tue, Feb 04, 2025 at 02:42:52PM -0800, Jakub Kicinski wrote:
> On Mon, 3 Feb 2025 13:09:29 -0800 Tony Nguyen wrote:
> > Now changing queues using ethtool is also changing MSI-X. If there is
> > enough MSI-X it is always one to one. When there is not enough there
> > will be more queues than MSI-X. There is a lack of ability to set how
> > many queues should be used per MSI-X. Maybe we should introduce another
> > ethtool param for it? Sth like queues_per_vector?
>
> It's probably okay for today. AFAIU ethtool channels basically
> correspond to IRQs. As the queue API matures we'll have
> the ability to allocate more queues for "channel" == IRQ / event
> queue.
>
Ok, thanks for explanation.
> > The following are changes since commit c2933b2befe25309f4c5cfbea0ca80909735fd76:
> > Merge tag 'net-6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
> > and are available in the git repository at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 100GbE
>
> Tony, the patches in your tree are missing your SoB, and I suspect
> you may need the same PR to get pulled into RDMA, so I'm not applying
> from the list... Please respin.
> --
> pw-bot: cr
prev parent reply other threads:[~2025-02-05 5:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:09 [PATCH net-next 0/9][pull request] ice: managing MSI-X in driver Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 1/9] ice: count combined queues using Rx/Tx count Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 2/9] ice: devlink PF MSI-X max and min parameter Tony Nguyen
2025-02-03 21:48 ` David Laight
2025-02-04 6:06 ` Michal Swiatkowski
2025-02-04 18:41 ` David Laight
2025-02-05 7:40 ` Michal Swiatkowski
2025-02-04 22:35 ` Jakub Kicinski
2025-02-05 5:46 ` Michal Swiatkowski
2025-02-03 21:09 ` [PATCH net-next 3/9] ice: remove splitting MSI-X between features Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 4/9] ice: get rid of num_lan_msix field Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 5/9] ice, irdma: move interrupts code to irdma Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 6/9] ice: treat dyn_allowed only as suggestion Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 7/9] ice: enable_rdma devlink param Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 8/9] ice: simplify VF MSI-X managing Tony Nguyen
2025-02-03 21:09 ` [PATCH net-next 9/9] ice: init flow director before RDMA Tony Nguyen
2025-02-04 22:42 ` [PATCH net-next 0/9][pull request] ice: managing MSI-X in driver Jakub Kicinski
2025-02-04 23:07 ` Tony Nguyen
2025-02-05 5:46 ` Michal Swiatkowski [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=Z6L7LPIxHXPz2/ih@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jgg@ziepe.ca \
--cc=jiri@resnulli.us \
--cc=konrad.knitter@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=marcin.szycik@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.nat.hpm.dev@intel.com \
--cc=pabeni@redhat.com \
--cc=pio.raczynski@gmail.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=tatyana.e.nikolova@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 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.