public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	Eric Northup <digitaleric@google.com>,
	Will Deacon <will.deacon@arm.com>,
	Marc Zyngier <marc.zyngier@arm.com>, KVM <kvm@vger.kernel.org>,
	Asias He <asias@redhat.com>,
	jasowang@redhat.com, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] kvm tools: virtio-net mergable rx buffers
Date: Wed, 24 Apr 2013 12:23:28 +0300	[thread overview]
Message-ID: <20130424092328.GC11245@redhat.com> (raw)
In-Reply-To: <CAOJsxLFwL+GvC1B14K4F+Q=73SLiyu9S_bV43eP3MOE5dY94BQ@mail.gmail.com>

On Wed, Apr 24, 2013 at 09:51:57AM +0300, Pekka Enberg wrote:
> Hi,
> 
> On 04/23/2013 12:35 PM, Eric Northup wrote:
> >> Do you care about guests with drivers that don't negotiate
> >> VIRTIO_NET_F_MRG_RXBUF?
> 
> On Wed, Apr 24, 2013 at 5:51 AM, Sasha Levin <sasha.levin@oracle.com> wrote:
> > We usually try to keep backward compatibility, but in this case
> > mergable RX buffers are about 5 years old now, so it's safe to
> > assume they'll be running in any guest.
> >
> > Unless there is a specific reason to allow working without them
> > I'd rather keep the code simple in this case.
> 
> Are there such guests around? What's the failure scenario for them
> after this patch?
> 
>                         Pekka

Warning: have not looked at the patch, just a general comment.

I think it's reasonable to assume embedded guests such as PXE won't
negotiate any features.  And, running old guests is one of the reasons
people use virtualization at all. So 5 years is not a lot.

In any case, stick to the device spec please, if you want it changed
please send a spec patch, don't deviate from it randomly.

-- 
MST


  reply	other threads:[~2013-04-24  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  0:32 [PATCH] kvm tools: virtio-net mergable rx buffers Sasha Levin
2013-04-23  9:06 ` Pekka Enberg
2013-04-23 14:19   ` Asias He
2013-04-23 15:01 ` Sasha Levin
2013-04-23 16:35 ` Eric Northup
2013-04-24  2:51   ` Sasha Levin
2013-04-24  6:51     ` Pekka Enberg
2013-04-24  9:23       ` Michael S. Tsirkin [this message]
2013-04-29  0:44         ` Rusty Russell
2013-04-29  2:36           ` Sasha Levin
2013-04-24  5:32 ` Asias He
2013-04-24  9:35   ` 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=20130424092328.GC11245@redhat.com \
    --to=mst@redhat.com \
    --cc=asias@redhat.com \
    --cc=digitaleric@google.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=penberg@kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sasha.levin@oracle.com \
    --cc=will.deacon@arm.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