[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL+tcoAP=Jg3pXO-_46w5CbrGnGVzHf4woqg3bQNCrb8SMhnrw@mail.gmail.com>
Date: Thu, 13 Jun 2024 22:55:16 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
davem@...emloft.net, dsahern@...nel.org, mst@...hat.com, jasowang@...hat.com,
xuanzhuo@...ux.alibaba.com, eperezma@...hat.com, leitao@...ian.org
Cc: netdev@...r.kernel.org, Jason Xing <kernelxing@...cent.com>
Subject: Re: [PATCH net-next v3] net: dqs: introduce IFF_NO_BQL private flag
for non-BQL drivers
On Thu, Jun 13, 2024 at 10:35 AM Jason Xing <kerneljasonxing@...il.com> wrote:
>
> From: Jason Xing <kernelxing@...cent.com>
>
> Since commit 74293ea1c4db6 ("net: sysfs: Do not create sysfs for non
> BQL device") limits the non-BQL driver not creating byte_queue_limits
> directory, I found there is one exception, namely, virtio-net driver,
> which should also be limited in netdev_uses_bql(). Let me give it a
> try first.
>
> I decided to introduce a NO_BQL bit because:
> 1) it can help us limit virtio-net driver for now.
> 2) if we found another non-BQL driver, we can take it into account.
> 3) we can replace all the driver meeting those two statements in
> netdev_uses_bql() in future.
>
> For now, I would like to make the first step to use this new bit for dqs
> use instead of replacing/applying all the non-BQL drivers in one go.
>
> As Jakub said, "netdev_uses_bql() is best effort", I think, we can add
> new non-BQL drivers as soon as we find one.
>
> After this patch, there is no byte_queue_limits directory in virtio-net
> driver.
>
> Signed-off-by: Jason Xing <kernelxing@...cent.com>
Hello Jakub,
I wonder why the status of this patch was changed to 'Changes
Requested'? Is there anything else I should adjust?
Thanks,
Jason
Powered by blists - more mailing lists