From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
ohering@suse.com, jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org, apw@canonical.com,
jasowang@redhat.com
Subject: Re: [PATCH V1 1/7] Drivers: hv: vmbus: Implement multi-channel support
Date: Thu, 16 May 2013 10:01:13 -0400 [thread overview]
Message-ID: <20130516140113.GB2629@kroah.com> (raw)
In-Reply-To: <1368706879-32321-1-git-send-email-kys@microsoft.com>
On Thu, May 16, 2013 at 05:21:13AM -0700, K. Y. Srinivasan wrote:
> Starting with Win8, the host supports multiple sub-channels for a given
> device. As in the past, the initial channel offer specifies the device and
> is associated with both the type and the instance GUIDs. For performance
> critical devices, the host may support multiple sub-channels. The sub-channels
> share the same type and instance GUID as the primary channel. The number of
> sub-channels offerrred to the guest depends on the number of virtual CPUs
> assigned to the guest. The guest can request the creation of these sub-channels
> and once created and opened, the guest can distribute the traffic across all
> the channels (the primary and the sub-channels). A request sent on a sub-channel
> will have the response delivered on the same sub-channel.
>
> At channel (sub-channel) creation we bind the channel interrupt to a CPU and
> with this sub-channel support we will be able to spread the interrupt load
> of a given device across all available CPUs.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2013-05-16 14:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 12:19 [PATCH V1 0/7] Drivers: hv/scsi: Implement multi-channel support K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 1/7] Drivers: hv: vmbus: " K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 2/7] Drivers: hv: Add the GUID fot synthetic fiber channel device K. Y. Srinivasan
2013-05-16 14:00 ` Greg KH
2013-05-16 12:21 ` [PATCH V1 3/7] Drivers: scsi: storvsc: Make the scsi timeout a module parameter K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 4/7] Drivers: scsi: storvsc: Update the storage protocol to win8 level K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 5/7] Drivers: scsi: storvsc: Implement multi-channel support K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 6/7] Drivers: scsi: storvsc: Support FC devices K. Y. Srinivasan
2013-05-16 12:21 ` [PATCH V1 7/7] Drivers: scsi: storvsc: Increase the value of STORVSC_MAX_IO_REQUESTS K. Y. Srinivasan
2013-05-16 12:02 ` Dan Carpenter
2013-05-16 13:37 ` KY Srinivasan
2013-05-16 13:55 ` Dan Carpenter
2013-05-16 14:01 ` KY Srinivasan
2013-05-16 14:08 ` Dan Carpenter
2013-05-16 14:01 ` Greg KH [this message]
2013-05-23 17:26 ` [PATCH V1 1/7] Drivers: hv: vmbus: Implement multi-channel support KY Srinivasan
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=20130516140113.GB2629@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.com \
/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