From: Joe Damato <jdamato@fastly.com>
To: Gal Pressman <gal@nvidia.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
Tariq Toukan <ttoukan.linux@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rrameshbabu@nvidia.com, Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"open list:MELLANOX MLX5 core VPI driver"
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH net-next] eth: mlx5: link NAPI instances to queues and IRQs
Date: Wed, 7 Feb 2024 06:25:29 -0800 [thread overview]
Message-ID: <20240207142529.GA12897@fastly.com> (raw)
In-Reply-To: <b3c595d8-b30a-41ac-bb82-c1264678b3c4@nvidia.com>
On Wed, Feb 07, 2024 at 08:59:18AM +0200, Gal Pressman wrote:
> On 06/02/2024 21:23, Joe Damato wrote:
> >> The per queue coalesce series is going through internal code review, and is
> >> expected to also be ready in a matter of a few weeks.
> >
> > OK, great. Thanks for letting me know; we are definitely interested in
> > using this feature.
>
> Hi Joe,
> Can you please share some details about your usecase for this feature?
It was outlined in the cover letter for the RFC [1].
But, briefly: we set a number of queues (say 16) via ethtool. We then
create a series of n-tuple filters directing certain flows to queues 0-7
via a custom RSS context. The remaining queues, 8-15 are for all other
flows via the default RSS context.
Queues 0-7 are used with busy polling from userland so we want those queues
to have a larger rx/tx-usecs rx/tx-frames than queues 8-15.
We implemented basic support for this in the RFC we sent to the mailing
list.
[1]: https://lore.kernel.org/lkml/20230823223121.58676-1-dev@nalramli.com/
next prev parent reply other threads:[~2024-02-07 14:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:03 [PATCH net-next] eth: mlx5: link NAPI instances to queues and IRQs Joe Damato
2024-02-06 1:09 ` Rahul Rameshbabu
2024-02-06 1:32 ` Joe Damato
2024-02-06 1:33 ` Rahul Rameshbabu
2024-02-06 1:41 ` Joe Damato
2024-02-06 1:44 ` Rahul Rameshbabu
2024-02-06 1:56 ` Joe Damato
2024-02-06 2:38 ` Rahul Rameshbabu
2024-02-06 2:51 ` Joe Damato
2024-02-06 8:11 ` Tariq Toukan
2024-02-06 17:12 ` Joe Damato
2024-02-06 19:10 ` Tariq Toukan
2024-02-06 19:23 ` Joe Damato
2024-02-07 6:59 ` Gal Pressman
2024-02-07 14:25 ` Joe Damato [this message]
2024-02-07 14:31 ` Dave Taht
2024-02-07 13:23 ` Tariq Toukan
2024-02-07 14:40 ` Joe Damato
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=20240207142529.GA12897@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ttoukan.linux@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: 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.