[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c1b647dc-6832-f8a2-baad-0e3a32ceef94@nvidia.com>
Date: Tue, 11 Jul 2023 10:13:33 +0800
From: Gavin Li <gavinl@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: mst@...hat.com, jasowang@...hat.com, xuanzhuo@...ux.alibaba.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
ast@...nel.org, daniel@...earbox.net, hawk@...nel.org,
john.fastabend@...il.com, jiri@...dia.com, dtatulea@...dia.com,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [RESEND PATCH net-next-mlx5 V1 0/4] virtio_net: add per queue
interrupt coalescing support
On 7/11/2023 2:09 AM, Jakub Kicinski wrote:
> External email: Use caution opening links or attachments
>
>
> On Mon, 10 Jul 2023 12:58:46 +0300 Gavin Li wrote:
>> Currently, coalescing parameters are grouped for all transmit and receive
>> virtqueues. This patch series add support to set or get the parameters for
>> a specified virtqueue.
>>
>> When the traffic between virtqueues is unbalanced, for example, one virtqueue
>> is busy and another virtqueue is idle, then it will be very useful to
>> control coalescing parameters at the virtqueue granularity.
> Why did you resend this, disobeying the posting rules:
>
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
>
> and what is net-next-mlx5? :|
I thought I made a mistake to use a wrong branch net-next. Please ignore
this mail thread then. Sorry for the confusion.
Powered by blists - more mailing lists