Sure. We have been working on NPA for a while and have the code internally up and running. Let me sync up internally on how and when we can provide the vmxnet3 driver code so that people can look at it. On Tue, May 04, 2010 at 05:32:36PM -0700, David Miller wrote: > Date: Tue, 4 May 2010 17:32:36 -0700 > From: David Miller <davem@xxxxxxxxxxxxx> > To: Pankaj Thakkar <pthakkar@xxxxxxxxxx> > CC: "shemminger@xxxxxxxxxx" <shemminger@xxxxxxxxxx>, > "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, > "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, > "virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx" > <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>, > "pv-drivers@xxxxxxxxxx" <pv-drivers@xxxxxxxxxx>, > Shreyas Bhatewara <sbhatewara@xxxxxxxxxx> > Subject: Re: RFC: Network Plugin Architecture (NPA) for vmxnet3 > > From: Pankaj Thakkar <pthakkar@xxxxxxxxxx> > Date: Tue, 4 May 2010 17:18:57 -0700 > > > The purpose of this email is to introduce the architecture and the > > design principles. The overall project involves more than just > > changes to vmxnet3 driver and hence we though an overview email > > would be better. Once people agree to the design in general we > > intend to provide the code changes to the vmxnet3 driver. > > Stephen's point is that code talks and bullshit walks. > > Talk about high level designs rarely gets any traction, and often goes > nowhere. Give us an example implementation so there is something > concrete for us to sink our teeth into. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
