[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240926155603.GH4029621@kernel.org>
Date: Thu, 26 Sep 2024 16:56:03 +0100
From: Simon Horman <horms@...nel.org>
To: Joe Damato <jdamato@...tly.com>, netdev@...r.kernel.org,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
"open list:Hyper-V/Azure CORE AND DRIVERS" <linux-hyperv@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC net-next 1/1] hv_netvsc: Link queues to NAPIs
On Thu, Sep 26, 2024 at 08:42:32AM -0700, Joe Damato wrote:
> On Thu, Sep 26, 2024 at 04:10:24PM +0100, Simon Horman wrote:
> > On Tue, Sep 24, 2024 at 11:48:51PM +0000, Joe Damato wrote:
> > > Use netif_queue_set_napi to link queues to NAPI instances so that they
> > > can be queried with netlink.
> > >
> > > Signed-off-by: Joe Damato <jdamato@...tly.com>
> > > ---
> > > drivers/net/hyperv/netvsc.c | 11 ++++++++++-
> > > drivers/net/hyperv/rndis_filter.c | 9 +++++++--
> > > 2 files changed, 17 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/net/hyperv/netvsc.c b/drivers/net/hyperv/netvsc.c
> > > index 2b6ec979a62f..ccaa4690dba0 100644
> > > --- a/drivers/net/hyperv/netvsc.c
> > > +++ b/drivers/net/hyperv/netvsc.c
> > > @@ -712,8 +712,11 @@ void netvsc_device_remove(struct hv_device *device)
> > > for (i = 0; i < net_device->num_chn; i++) {
> > > /* See also vmbus_reset_channel_cb(). */
> > > /* only disable enabled NAPI channel */
> > > - if (i < ndev->real_num_rx_queues)
> > > + if (i < ndev->real_num_rx_queues) {
> > > + netif_queue_set_napi(ndev, i, NETDEV_QUEUE_TYPE_TX, NULL);
> > > + netif_queue_set_napi(ndev, i, NETDEV_QUEUE_TYPE_RX, NULL);
> >
> > Hi Joe,
> >
> > When you post a non-RFC version of this patch, could you consider
> > line-wrapping the above to 80 columns, as is still preferred for
> > Networking code?
> >
> > There is an option to checkpatch that will warn you about this.
>
> Thanks for letting me know.
>
> I run checkpatch.pl --strict and usually it seems to let me know if
> I am over 80, but maybe there's another option I need?
At some point the default changed from 80 to 100.
So these days --max-line-length=80 is needed to detect this.
--strict is also good :)
Powered by blists - more mailing lists