Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Tiwei Bie <tiwei.bie@intel.com>,
	cohuck@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
	jasowang@redhat.com, pasic@linux.vnet.ibm.com,
	virtio-dev@lists.oasis-open.org, dan.daly@intel.com,
	cunming.liang@intel.com, zhihong.wang@intel.com
Subject: Re: [virtio-dev] [RFC] content: tweak VIRTIO_F_IO_BARRIER
Date: Tue, 26 Jun 2018 00:27:26 +0300	[thread overview]
Message-ID: <20180626002306-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <72351a30-480e-b160-9774-c0b880230c1d@linux.ibm.com>

On Mon, Jun 25, 2018 at 08:40:55PM +0200, Halil Pasic wrote:
> 
> 
> On 06/25/2018 07:42 PM, Michael S. Tsirkin wrote:
> > On Mon, Jun 25, 2018 at 06:07:17PM +0200, Halil Pasic wrote:
> > > 
> > > 
> > > On 06/25/2018 02:24 PM, Tiwei Bie wrote:
> > > > VIRTIO_F_IO_BARRIER was proposed recently to allow
> [..]
> > > > +  \item[VIRTIO_F_REAL_DEVICE(36)] This feature indicates
> > > > +  that the device doesn't allow the driver to assume the
> > > > +  device is implemented in software and runs on host CPU.
> > > > +  When devices are implemented in software and run on host
> > > > +  CPU, some optimizations can be done in drivers and yield
> > > 
> > > s/optimizations/optimization/ ?
> > 
> > Why?
> > 
> 
> My spell-checker complains but after searching the internet it
> 'optimizations' seems like a legit plural. However
> https://en.oxforddictionaries.com/definition/optimization
> does state 'mass noun' (that is uncountable) but then there
> is an example with countable :S. English is not my strong
> side.
> 
> Regards,
> Halil


It's like e.g. coffee.

So "some optimization" means "a little".

"Some optimizations" means "not all".

-- 
MST

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-06-25 21:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 12:24 [virtio-dev] [RFC] content: tweak VIRTIO_F_IO_BARRIER Tiwei Bie
2018-06-25 16:07 ` Halil Pasic
2018-06-25 17:42   ` Michael S. Tsirkin
2018-06-25 18:40     ` Halil Pasic
2018-06-25 21:27       ` Michael S. Tsirkin [this message]
2018-06-26 13:48         ` Halil Pasic
2018-06-25 19:19 ` [virtio-dev] " Michael S. Tsirkin
2018-06-26 13:47   ` Halil Pasic
2018-06-26 18:19     ` Tiwei Bie
2018-06-26 18:39       ` Michael S. Tsirkin
2018-06-27 16:08         ` Cornelia Huck
2018-06-28  8:52           ` Tiwei Bie
2018-06-28 12:56             ` Jason Wang
2018-06-29  4:21               ` Michael S. Tsirkin
2018-06-29  6:11                 ` Jason Wang
2018-06-29  4:20             ` Michael S. Tsirkin
2018-07-16 11:04               ` Tiwei Bie
2018-08-27 18:36                 ` Michael S. Tsirkin
2018-07-01  3:23           ` Michael S. Tsirkin

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=20180626002306-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=cunming.liang@intel.com \
    --cc=dan.daly@intel.com \
    --cc=jasowang@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=tiwei.bie@intel.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=zhihong.wang@intel.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