From: Christoph Hellwig <hch@infradead.org>
To: Jason Wang <jasowang@redhat.com>
Cc: Vitaly Mayatskih <v.mayatskih@gmail.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stefanha@redhat.com
Subject: Re: [PATCH 0/1] vhost: add vhost_blk driver
Date: Mon, 5 Nov 2018 23:13:49 -0800 [thread overview]
Message-ID: <20181106071349.GA5526@infradead.org> (raw)
In-Reply-To: <57eefa62-7e66-786d-441c-5dd6b0d451a5@redhat.com>
On Tue, Nov 06, 2018 at 10:45:08AM +0800, Jason Wang wrote:
> > Storage industry is shifting away from SCSI, which has a scaling
> > problem.
>
>
> Know little about storage. For scaling, do you mean SCSI protocol itself? If
> not, it's probably not a real issue for virtio-scsi itself.
The above is utter bullshit. There is a big NVMe hype, but it is not
because "SCSI has a scaling problem", but because the industry can sell
a new thing, and the standardization body seems easier to work with.
next prev parent reply other threads:[~2018-11-06 7:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 18:21 [PATCH 0/1] vhost: add vhost_blk driver Vitaly Mayatskikh
2018-11-02 18:21 ` [PATCH 1/1] Add " Vitaly Mayatskikh
2018-11-02 18:36 ` Michael S. Tsirkin
2018-11-02 18:36 ` Michael S. Tsirkin
2018-11-02 19:24 ` Vitaly Mayatskih
2018-11-02 20:38 ` Michael S. Tsirkin
2018-11-02 20:38 ` Michael S. Tsirkin
2018-11-03 2:50 ` kbuild test robot
2018-11-03 2:50 ` kbuild test robot
2018-11-03 2:50 ` kbuild test robot
2018-11-06 16:03 ` Stefan Hajnoczi
2018-11-06 16:03 ` Stefan Hajnoczi
2018-11-06 19:47 ` Vitaly Mayatskih
2018-11-02 18:26 ` [PATCH 0/1] vhost: add " Michael S. Tsirkin
2018-11-02 18:31 ` Vitaly Mayatskih
2018-11-05 14:02 ` Christian Borntraeger
2018-11-05 14:02 ` Christian Borntraeger
2018-11-05 14:21 ` Vitaly Mayatskih
2018-11-06 15:40 ` Stefan Hajnoczi
2018-11-06 15:40 ` Stefan Hajnoczi
2018-11-06 18:46 ` Denis Lunev
2018-11-06 20:08 ` Vitaly Mayatskih
2018-11-02 18:26 ` Michael S. Tsirkin
2018-11-04 11:57 ` Maxim Levitsky
2018-11-04 16:40 ` Vitaly Mayatskih
2018-11-05 11:55 ` Maxim Levitsky
2018-11-05 3:00 ` Jason Wang
2018-11-05 3:23 ` Vitaly Mayatskih
2018-11-06 2:45 ` Jason Wang
2018-11-06 2:45 ` Jason Wang
2018-11-06 2:56 ` Vitaly Mayatskih
2018-11-06 7:13 ` Christoph Hellwig [this message]
2018-11-06 21:41 ` Paolo Bonzini
2018-11-06 21:41 ` Paolo Bonzini
2018-11-06 7:13 ` Christoph Hellwig
2018-11-05 15:48 ` Christian Borntraeger
2018-11-05 15:48 ` Christian Borntraeger
2018-11-05 16:15 ` Vitaly Mayatskih
2018-11-06 15:21 ` Stefan Hajnoczi
2018-11-06 15:21 ` Stefan Hajnoczi
2018-11-05 3:00 ` Jason Wang
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=20181106071349.GA5526@infradead.org \
--to=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=v.mayatskih@gmail.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.