[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49D4B87D.2000202@redhat.com>
Date: Thu, 02 Apr 2009 16:07:09 +0300
From: Avi Kivity <avi@...hat.com>
To: Gregory Haskins <ghaskins@...ell.com>
CC: Rusty Russell <rusty@...tcorp.com.au>,
Herbert Xu <herbert@...dor.apana.org.au>,
anthony@...emonkey.ws, andi@...stfloor.org,
linux-kernel@...r.kernel.org, agraf@...e.de, pmullaney@...ell.com,
pmorreale@...ell.com, netdev@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC PATCH 00/17] virtual-bus
Gregory Haskins wrote:
> Rusty Russell wrote:
>
>> On Thursday 02 April 2009 21:36:07 Gregory Haskins wrote:
>>
>>
>>> You do not need to know when the packet is copied (which I currently
>>> do). You only need it for zero-copy (of which I would like to support,
>>> but as I understand it there are problems with the reliability of proper
>>> callback (i.e. skb->destructor).
>>>
>>>
>> But if you have a UP guest,
>>
>
> I assume you mean UP host ;)
>
>
I think Rusty did mean a UP guest, and without schedule-and-forget.
> Hmm..well I was hoping to be able to work with you guys to make my
> proposal fit this role. If there is no interest in that, I hope that my
> infrastructure itself may still be considered for merging (in *some*
> tree, not -kvm per se) as I would prefer to not maintain it out of tree
> if it can be avoided.
The problem is that we already have virtio guest drivers going several
kernel versions back, as well as Windows drivers. We can't keep
changing the infrastructure under people's feet.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists