From: Haiyang Zhang <haiyangz@microsoft.com>
To: Greg KH <greg@kroah.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net-next, v2] Add support for netvsc build without CONFIG_SYSFS flag
Date: Thu, 8 May 2014 20:41:32 +0000 [thread overview]
Message-ID: <416d12ac27914bb98baa1891509d641c@DFM-DB3MBX15-06.exchange.corp.microsoft.com> (raw)
In-Reply-To: <20140508200352.GB8847@kroah.com>
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Thursday, May 8, 2014 4:04 PM
> To: Haiyang Zhang
> Cc: davem@davemloft.net; netdev@vger.kernel.org; olaf@aepfle.de;
> jasowang@redhat.com; driverdev-devel@linuxdriverproject.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH net-next, v2] Add support for netvsc build without
> CONFIG_SYSFS flag
>
> On Thu, May 08, 2014 at 01:41:33PM -0700, Haiyang Zhang wrote:
> > This change ensures the driver can be built successfully without the
> > CONFIG_SYSFS flag.
> > MS-TFS: 182270
> >
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > Reviewed-by: K. Y. Srinivasan <kys@microsoft.com>
> > ---
> > drivers/net/hyperv/hyperv_net.h | 28 ++++++++++++++++++++++++++++
> > drivers/net/hyperv/netvsc_drv.c | 13 +++++++------
> > drivers/net/hyperv/rndis_filter.c | 4 ++--
> > 3 files changed, 37 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/net/hyperv/hyperv_net.h
> > b/drivers/net/hyperv/hyperv_net.h index 4b7df5a..02358cb 100644
> > --- a/drivers/net/hyperv/hyperv_net.h
> > +++ b/drivers/net/hyperv/hyperv_net.h
> > @@ -87,6 +87,8 @@ struct ndis_recv_scale_cap { /*
> > NDIS_RECEIVE_SCALE_CAPABILITIES */ #define HASH_KEYLEN
> > NDIS_RSS_HASH_SECRET_KEY_MAX_SIZE_REVISION_2
> > extern u8 netvsc_hash_key[];
> >
> > +extern unsigned int netvsc_num_queue;
> > +
> > struct ndis_recv_scale_param { /* NDIS_RECEIVE_SCALE_PARAMETERS */
> > struct ndis_obj_header hdr;
> >
> > @@ -178,6 +180,32 @@ struct rndis_device {
> > unsigned char hw_mac_adr[ETH_ALEN];
> > };
> >
> > +static inline void netvsc_record_rx_queue(struct sk_buff *skb,
> > + struct hv_netvsc_packet *packet,
> > + struct net_device *ndev)
> > +{
> > +#ifdef CONFIG_SYSFS
> > + skb_record_rx_queue(skb, packet->channel->
> > + offermsg.offer.sub_channel_index %
> > + ndev->real_num_rx_queues);
> > +#endif
>
> Really? Do all other wireless drivers have this type of #ifdef needed?
>
> > +}
> > +
> > +static inline void netvsc_show_num_queue(struct device *dev,
> > + struct net_device *ndev)
> > +{
> > +#ifdef CONFIG_SYSFS
> > + dev_info(dev, "real num tx,rx queues:%u, %u\n",
> > + ndev->real_num_tx_queues, ndev->real_num_rx_queues);
> #endif
>
> Do network drivers really spam the kernel log with this type of thing?
> If you have sysfs, why is this needed in the kernel log?
>
> > +}
> > +
> > +static inline void netvsc_set_num_queue(unsigned int *nq) { #ifdef
> > +CONFIG_SYSFS
> > + *nq = num_online_cpus();
> > +#endif
> > +}
>
> I really feel that something is odd here...
I looked around the other drivers, and the netif_set_real_num_rx_queues()
function. It's already switched to no-op without CONFIG_SYSFS flag. So I will
rely on this, and don't have to handle the flag in my code.
Also, the dev_info can be removed.
Thanks,
- Haiyang
next prev parent reply other threads:[~2014-05-08 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 20:41 [PATCH net-next,v2] " Haiyang Zhang
2014-05-08 20:03 ` [PATCH net-next, v2] " Greg KH
2014-05-08 20:41 ` Haiyang Zhang [this message]
2014-05-08 20:44 ` [PATCH net-next,v2] " David Miller
2014-05-08 20:50 ` Haiyang Zhang
2014-05-11 13:07 ` Ben Hutchings
2014-05-11 22:35 ` Haiyang Zhang
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=416d12ac27914bb98baa1891509d641c@DFM-DB3MBX15-06.exchange.corp.microsoft.com \
--to=haiyangz@microsoft.com \
--cc=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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®