Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Ronciak, John
, 2014 11:21 AM > To: Rustad, Mark D > Cc: Ronciak, John; e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] Bringing down igb interface causes 200ms > latency in unrelated processes > > Yes, I think that's the issue. With our 20ms timeslots it was taking >

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Aaron Brice
On Wed, Mar 26, 2014 at 3:59 PM, Rustad, Mark D wrote: > I don't have any experience with the igb driver myself, but a quick look > shows that it is only taking the rtnl lock in two places, and those probably > are not your issue. It would be nice if the rtnl lock were to be broken down > into

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Rustad, Mark D
On Mar 26, 2014, at 3:36 PM, Aaron Brice wrote: > Well, I got past the ioctl part but it seems that we're also doing > some QoS stuff using netlink sockets that is getting delayed also, and > I can't get rid of the rtnl lock there.. Is there anything that can > be done on the driver side? 200ms

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Aaron Brice
Well, I got past the ioctl part but it seems that we're also doing some QoS stuff using netlink sockets that is getting delayed also, and I can't get rid of the rtnl lock there.. Is there anything that can be done on the driver side? 200ms seems like a long time to be holding the lock.. Aaron O

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Aaron Brice
Yes, I think that's the issue. With our 20ms timeslots it was taking too long to do a bunch of reads so we added an ioctl to the tap driver to read a bunch of packets into a buffer. I think we can remove the rtnl lock for this particular ioctl. We didn't see an issue with the e1000 motherboard i

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Rustad, Mark D
On Mar 26, 2014, at 10:24 AM, Aaron Brice wrote: > On Tue, Mar 25, 2014 at 10:39 PM, Ronciak, John > wrote: >> How are the different PCIe slots connected into the system? In a lot of >> cases some of the slots are not all equal in terms of how they are laid out >> in the system. If you move

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-26 Thread Aaron Brice
On Tue, Mar 25, 2014 at 10:39 PM, Ronciak, John wrote: > How are the different PCIe slots connected into the system? In a lot of > cases some of the slots are not all equal in terms of how they are laid out > in the system. If you move the interface doing the 20ms read to a NIC in a > differe

Re: [E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-25 Thread Ronciak, John
> -Original Message- > From: Aaron Brice [mailto:aaron.br...@gmail.com] > Sent: Tuesday, March 25, 2014 5:54 PM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] Bringing down igb interface causes 200ms latency > in unrelated processes > > I have

[E1000-devel] Bringing down igb interface causes 200ms latency in unrelated processes

2014-03-25 Thread Aaron Brice
I have a 12 CPU server with 3 4-port 82576 network cards (12 ports total using igb driver). It's running Debian 7 (3.2 kernel with the realtime patches). I have a process on that system that is reading from a virtual tap interface every 20ms (using boost::asio) and writing udp packets out one of