Re: Xen virtual network (Netfront) driver

On Mon, Jan 25, 2016 at 12:04:03PM +0100, Mike Belopuhov wrote: > On 25 January 2016 at 01:38, Jonathon Sisson wrote: > > Not certain if this is debug output put there intentionally or > > Yes. > > > if this is some error condition? > > It is. Transmission is stuck and these

Re: Xen virtual network (Netfront) driver

On 25 January 2016 at 01:38, Jonathon Sisson wrote: > tech@, > > I've uploaded a few of the dmesgs gathered to dmesgd.nycbug.org: > > http://dmesgd.nycbug.org/index.cgi?action=dmesgd=index=Jonathon > > Currently I have m4.10xlarge, c4.8xlarge, m3.medium, and t2.nano > uploaded

Re: Xen virtual network (Netfront) driver

Hi Jonathon, Thanks a lot for taking your time to test this. On 24 January 2016 at 06:49, Jonathon Sisson wrote: > On Sat, Jan 23, 2016 at 02:18:17PM -0800, Jonathon Sisson wrote: >> Speaking of testing, is there any particular area non-devs could >> assist with at this time?

Re: Xen virtual network (Netfront) driver

On Sun, Jan 24, 2016 at 02:16:37PM +0100, Mike Belopuhov wrote: > Hi Jonathon, > > Thanks a lot for taking your time to test this. > No, thank you guys for all of the work you're doing to get this working. I'm just a user heh. > > Trying newer kernels would be the most helpful. I've just

Re: Xen virtual network (Netfront) driver

On 24 January 2016 at 20:55, Jonathon Sisson wrote: > On Sun, Jan 24, 2016 at 02:16:37PM +0100, Mike Belopuhov wrote: >> Hi Jonathon, >> >> Thanks a lot for taking your time to test this. >> > No, thank you guys for all of the work you're doing to get > this working. I'm just a

Re: Xen virtual network (Netfront) driver

On Sun, Jan 24, 2016 at 09:08:32PM +0100, Mike Belopuhov wrote: > On 24 January 2016 at 20:55, Jonathon Sisson wrote: > > On Sun, Jan 24, 2016 at 02:16:37PM +0100, Mike Belopuhov wrote: > >> Hi Jonathon, > >> > >> Thanks a lot for taking your time to test this. > >> > > No, thank

Re: Xen virtual network (Netfront) driver

> On 23.01.2016, at 12:12, Anders Berggren wrote: > >> On 06 Jan 2016, at 18:49, Reyk Floeter wrote: >> - I didn't work on m4.10xlarge (see cvs:~reyk/dmesg.m4.10xlarge). > > I didn’t see any mentions of it in the dmesg >

Re: Xen virtual network (Netfront) driver

> On 06 Jan 2016, at 18:49, Reyk Floeter wrote: > - I didn't work on m4.10xlarge (see cvs:~reyk/dmesg.m4.10xlarge). I didn’t see any mentions of it in the dmesg https://gist.github.com/reyk/b372af303eb86bab3fee but could it be that those machine classes (*x*large-ish) uses

Re: Xen virtual network (Netfront) driver

On Sat, Jan 23, 2016 at 12:19:29PM +0100, Reyk Floeter wrote: > No, you have to *enable* SR-IOV in the image. > > Machines with the Intel NIC will not show any netfront in the device list via > XenStore (just try Ubuntu). > > Reyk That's correct, but I think what was being pointed out is that

Re: Xen virtual network (Netfront) driver

> On 23.01.2016, at 22:27, Jonathon Sisson wrote: > > On Sat, Jan 23, 2016 at 12:19:29PM +0100, Reyk Floeter wrote: >> No, you have to *enable* SR-IOV in the image. >> >> Machines with the Intel NIC will not show any netfront in the device list >> via XenStore (just try

Re: Xen virtual network (Netfront) driver

On Sat, Jan 23, 2016 at 10:57:21PM +0100, Reyk Floeter wrote: > > > On 23.01.2016, at 22:27, Jonathon Sisson wrote: > > > > On Sat, Jan 23, 2016 at 12:19:29PM +0100, Reyk Floeter wrote: > >> No, you have to *enable* SR-IOV in the image. > >> > >> Machines with the Intel NIC

Re: Xen virtual network (Netfront) driver

On Sat, Jan 23, 2016 at 02:18:17PM -0800, Jonathon Sisson wrote: > Speaking of testing, is there any particular area non-devs could > assist with at this time? Gathering dmesgs for different instance > types? > I decided to spin up one of each instance type and grab the console output in case it

Re: Xen virtual network (Netfront) driver

On Thu, 7 Jan 2016, Mike Belopuhov wrote: > On 7 January 2016 at 13:17, Mark Kettenis wrote: > >> From: Mike Belopuhov > >> Date: Thu, 7 Jan 2016 12:02:23 +0100 > >> > >> On 6 January 2016 at 17:58, Stefan Fritsch wrote: > >> > On

Re: Xen virtual network (Netfront) driver

> From: Mike Belopuhov > Date: Thu, 7 Jan 2016 12:02:23 +0100 > > On 6 January 2016 at 17:58, Stefan Fritsch wrote: > > On Wed, 6 Jan 2016, Mike Belopuhov wrote: > > > >> There's still stuff to do, but it receives and transmits reliably > >> (at least on

Re: Xen virtual network (Netfront) driver

On Wed, Jan 06, 2016 at 16:37 +0100, Mike Belopuhov wrote: > There's still stuff to do, but it receives and transmits reliably > (at least on modern Xen) so I'd like to get it in. Man page will > follow. > > OK? > Just noticed that a couple of debug printfs have sneaked in. I'm not going to

Xen virtual network (Netfront) driver

There's still stuff to do, but it receives and transmits reliably (at least on modern Xen) so I'd like to get it in. Man page will follow. OK? diff --git sys/arch/amd64/conf/GENERIC sys/arch/amd64/conf/GENERIC index fca4459..77e07cc 100644 --- sys/arch/amd64/conf/GENERIC +++

Re: Xen virtual network (Netfront) driver

On Wed, Jan 06, 2016 at 04:37:36PM +0100, Mike Belopuhov wrote: > There's still stuff to do, but it receives and transmits reliably > (at least on modern Xen) so I'd like to get it in. Man page will > follow. > > OK? > I can see it works now and as mentioned in icb: I just had the first

Re: Xen virtual network (Netfront) driver

On Wed, 6 Jan 2016, Mike Belopuhov wrote: > There's still stuff to do, but it receives and transmits reliably > (at least on modern Xen) so I'd like to get it in. Man page will > follow. I only had a quick glance at the code, but I have one comment about your use of memory barriers. The