From: Simon Horman <horms@kernel.org>
To: Joe Damato <jdamato@fastly.com>,
netdev@vger.kernel.org, "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"open list:Hyper-V/Azure CORE AND DRIVERS"
<linux-hyperv@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC net-next 1/1] hv_netvsc: Link queues to NAPIs
Date: Thu, 26 Sep 2024 16:56:03 +0100 [thread overview]
Message-ID: <20240926155603.GH4029621@kernel.org> (raw)
In-Reply-To: <ZvWA6BjwVfYXnDcA@LQ3V64L9R2>
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@fastly.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 :)
prev parent reply other threads:[~2024-09-26 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 23:48 [RFC net-next 0/1] hyperv: Link queues to NAPIs Joe Damato
2024-09-24 23:48 ` [RFC net-next 1/1] hv_netvsc: " Joe Damato
2024-09-25 19:39 ` Haiyang Zhang
2024-09-26 4:06 ` Shradha Gupta
2024-09-26 10:34 ` Shradha Gupta
2024-09-26 14:29 ` Haiyang Zhang
2024-09-26 15:41 ` Joe Damato
2024-09-26 15:53 ` Joe Damato
2024-09-26 16:45 ` Haiyang Zhang
2024-09-26 15:10 ` Simon Horman
2024-09-26 15:42 ` Joe Damato
2024-09-26 15:50 ` Joe Damato
2024-09-26 15:56 ` Simon Horman [this message]
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=20240926155603.GH4029621@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wei.liu@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).