From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO code removed upstream
Date: Thu, 01 Oct 2009 19:04:18 +0200 [thread overview]
Message-ID: <4AC4E112.1020709@redhat.com> (raw)
In-Reply-To: <1254416426.2920.41.camel@blaa>
On 10/01/2009 07:00 PM, Mark McLoughlin wrote:
> On Thu, 2009-10-01 at 18:49 +0200, Avi Kivity wrote:
>
>> On 09/30/2009 03:59 PM, Mark McLoughlin wrote:
>>
>>> I think we should keep the vlan stuff, just de-emphasise it.
>>>
>>>
>> Maybe we should do what X.org does, break it silently and remove it some
>> time later when no one complains.
>>
> Well, the 'silently' part isn't going to work now, is it?
>
Me and my big mouth.
> Anyway, I'm sure at least Jan would notice if his 'dump' backend stopped
> working
>
Patch it to use libpcap?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-01 17:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 16:50 virtio-net not working with the latest qemu-kvm git Sridhar Samudrala
2009-05-04 17:44 ` Alex Williamson
2009-05-05 8:56 ` [PATCH 1/1] qemu-kvm: virtio-net: Re-instate GSO code removed upstream Mark McLoughlin
2009-05-06 9:11 ` Avi Kivity
2009-09-29 20:45 ` Mark McLoughlin
2009-09-29 20:47 ` Mark McLoughlin
2009-09-30 6:24 ` Avi Kivity
2009-09-30 11:24 ` Glauber Costa
2009-09-30 11:24 ` Mark McLoughlin
2009-09-30 13:01 ` Anthony Liguori
2009-09-30 13:51 ` Christoph Hellwig
2009-09-30 13:55 ` Avi Kivity
2009-09-30 13:59 ` Mark McLoughlin
2009-09-30 19:15 ` Gerd Hoffmann
2009-10-01 6:59 ` [Qemu-devel] " Mark McLoughlin
2009-10-01 16:49 ` Avi Kivity
2009-10-01 17:00 ` Mark McLoughlin
2009-10-01 17:04 ` Avi Kivity [this message]
2009-05-05 8:56 ` virtio-net not working with the latest qemu-kvm git Mark McLoughlin
2009-05-06 9:12 ` Avi Kivity
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=4AC4E112.1020709@redhat.com \
--to=avi@redhat.com \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.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 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).