From: Gal Pressman <gal@nvidia.com>
To: Joe Damato <jdamato@fastly.com>, Tariq Toukan <tariqt@nvidia.com>
Cc: 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 08:59:18 +0200 [thread overview]
Message-ID: <b3c595d8-b30a-41ac-bb82-c1264678b3c4@nvidia.com> (raw)
In-Reply-To: <20240206192314.GA11982@fastly.com>
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?
next prev parent reply other threads:[~2024-02-07 6:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:03 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 [this message]
2024-02-07 14:25 ` Joe Damato
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=b3c595d8-b30a-41ac-bb82-c1264678b3c4@nvidia.com \
--to=gal@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®