From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@infradead.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
lf-virt <virtualization@lists.linux-foundation.org>,
kvm-devel <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Zhi Yong Wu <wuzhy@cn.ibm.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [RFC-v2 0/4] tcm_vhost+cmwq fabric driver code for-3.6
Date: Thu, 19 Jul 2012 08:00:44 +0200 [thread overview]
Message-ID: <5007A28C.602@redhat.com> (raw)
In-Reply-To: <50070A8D.7020203@us.ibm.com>
Il 18/07/2012 21:12, Anthony Liguori ha scritto:
> Is that true for all OSes? Linux may handle things gracefully if UNMAP
> starts throwing errors but that doesn't mean that Windows will.
There is so much USB crap (not just removable, think of ATA-to-USB
enclosures) that they have to deal with pretty much everything.
> Windows does this with a points system and I do believe that INQUIRY
> responses from any local disks are included in this tally.
INQUIRY responses (at least vendor/product/type) should not change.
Paolo
next prev parent reply other threads:[~2012-07-19 6:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 21:15 [RFC-v2 0/4] tcm_vhost+cmwq fabric driver code for-3.6 Nicholas A. Bellinger
2012-07-11 21:15 ` [RFC-v2 1/4] vhost: Separate vhost-net features from vhost features Nicholas A. Bellinger
2012-07-11 21:15 ` [RFC-v2 2/4] vhost: make vhost work queue visible Nicholas A. Bellinger
2012-07-11 21:15 ` [RFC-v2 3/4] vhost: Add vhost_scsi specific defines Nicholas A. Bellinger
2012-07-11 21:15 ` [RFC-v2 4/4] tcm_vhost: Initial merge for vhost level target fabric driver Nicholas A. Bellinger
2012-07-17 15:05 ` [RFC-v2 0/4] tcm_vhost+cmwq fabric driver code for-3.6 Michael S. Tsirkin
2012-07-17 18:55 ` Anthony Liguori
2012-07-17 19:00 ` Michael S. Tsirkin
2012-07-17 21:50 ` Nicholas A. Bellinger
2012-07-18 13:42 ` Anthony Liguori
2012-07-18 13:56 ` Paolo Bonzini
2012-07-18 15:33 ` Michael S. Tsirkin
2012-07-18 15:53 ` Christoph Hellwig
2012-07-18 16:00 ` Michael S. Tsirkin
2012-07-18 16:42 ` Rustad, Mark D
2012-07-18 17:17 ` Michael S. Tsirkin
2012-07-18 20:12 ` Rustad, Mark D
2012-07-18 16:00 ` Anthony Liguori
2012-07-18 16:47 ` James Bottomley
2012-07-18 19:12 ` Anthony Liguori
2012-07-19 6:00 ` Paolo Bonzini [this message]
2012-07-19 7:28 ` James Bottomley
2012-07-19 7:30 ` Paolo Bonzini
2012-07-18 22:45 ` Nicholas A. Bellinger
2012-07-17 21:17 ` Nicholas A. Bellinger
2012-07-17 21:34 ` Michael S. Tsirkin
2012-07-17 22:02 ` Nicholas A. Bellinger
2012-07-17 22:18 ` Michael S. Tsirkin
2012-07-17 22:37 ` Nicholas A. Bellinger
2012-07-17 23:11 ` Michael S. Tsirkin
2012-07-18 0:17 ` Nicholas A. Bellinger
2012-07-17 21:58 ` Michael S. Tsirkin
2012-07-17 22:04 ` Nicholas A. Bellinger
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=5007A28C.602@redhat.com \
--to=pbonzini@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wuzhy@cn.ibm.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;
as well as URLs for NNTP newsgroup(s).