[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49D487A6.407@redhat.com>
Date: Thu, 02 Apr 2009 12:38:46 +0300
From: Avi Kivity <avi@...hat.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: ghaskins@...ell.com, anthony@...emonkey.ws, andi@...stfloor.org,
linux-kernel@...r.kernel.org, agraf@...e.de, pmullaney@...ell.com,
pmorreale@...ell.com, rusty@...tcorp.com.au,
netdev@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC PATCH 00/17] virtual-bus
Herbert Xu wrote:
> On Thu, Apr 02, 2009 at 12:27:17PM +0300, Avi Kivity wrote:
>
>> If tap told us when the packets were actually transmitted, life would be
>> wonderful:
>>
>
> And why do we need this? Because we are in user space!
>
>
Why does a kernel solution not need to know when a packet is transmitted?
--
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