mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haiyang Zhang <haiyangz@microsoft.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	KY Srinivasan <kys@microsoft.com>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"driverdev-devel@linuxdriverproject.org" 
	<driverdev-devel@linuxdriverproject.org>
Subject: RE: [PATCH net-next,v2] Add support for netvsc build without CONFIG_SYSFS flag
Date: Sun, 11 May 2014 22:35:40 +0000	[thread overview]
Message-ID: <3fd83bc0e76c452386c15516a32c9cb3@DFM-DB3MBX15-06.exchange.corp.microsoft.com> (raw)
In-Reply-To: <1399813625.11946.138.camel@deadeye.wl.decadent.org.uk>

> ________________________________________
> From: Ben Hutchings <ben@decadent.org.uk>
> Sent: Sunday, May 11, 2014 9:07 AM
> To: Haiyang Zhang
> I think most other drivers have a 1-1 mapping between hardware RX queues
> and the RX queue indices reported to Linux.  It appears that in this
> case sub_channel_index is the 'hardware' queue number, but you think
> there is not a 1-1 mapping.  Why is that?

Actually, it is 1-1 mapping. The number of channels equals to the number of
queues. In my updated patch (v3) the unnecessary "% ndev->real_num_rx_queues"
has been removed.

Thanks,
- Haiyang

      reply	other threads:[~2014-05-11 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 20:41 Haiyang Zhang
2014-05-08 20:03 ` [PATCH net-next, v2] " Greg KH
2014-05-08 20:41   ` Haiyang Zhang
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 [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=3fd83bc0e76c452386c15516a32c9cb3@DFM-DB3MBX15-06.exchange.corp.microsoft.com \
    --to=haiyangz@microsoft.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.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®