On Tue, Aug 13, 2013 at 3:54 PM, Skidmore, Donald C
wrote:
> We were unable to recreate your failure here locally so I have some
> additional questions. First off you mentioned it was failing as far back as
> v3.9, was it ever working for you? If so bisecting would be really helpful
> as I m
Hey Bjorn,
Sorry for the slow reply I was on vacation last week and have been playing
catch up on my email.
We were unable to recreate your failure here locally so I have some additional
questions. First off you mentioned it was failing as far back as v3.9, was it
ever working for you? If
On 8/13/13 12:11 PM, "Gert-Jan Roskam" wrote:
>Since I think this is an issue with the 82576 chip, I am sending this to
>both the ptp and e1000 lists.
>
> A few months ago I had trouble with the INTEL 82576 and PTP. I got
>errors like: recvmsg tx timestamp failed: Resource temporarily
>unavailab
Since I think this is an issue with the 82576 chip, I am sending this to
both the ptp and e1000 lists.
A few months ago I had trouble with the INTEL 82576 and PTP. I got
errors like: recvmsg tx timestamp failed: Resource temporarily unavailable.
It was suggested to switch to a newer kernel, wh
On 08/13/2013 05:34 AM, Alexey Stoyanov wrote:
>> I am not an expert when it comes to setting up rate limiting. What you
>> would need to do is setup a qdisc and configure it to limit your
>> outgoing traffic. You can probably find more information on how to do
>> that on the web as what you are
> Also please try the nuttcp tool for bandwidth testing, as it reports the
> number of retransmits during each run.
>
> if the packets are overrunning a switch buffer somewhere in your network
> path, you can use apps like nuttcp to bandwidth limit udp sends in order
> to help troubleshoot what you
> I am not an expert when it comes to setting up rate limiting. What you
> would need to do is setup a qdisc and configure it to limit your
> outgoing traffic. You can probably find more information on how to do
> that on the web as what you are seeing could be buffer bloat. A good
> test for la
On Mon, 2013-08-12 at 16:40 -0700, Alexander Duyck wrote:
> On 08/12/2013 03:28 PM, Alexey Stoyanov wrote:
> > I done reload of ixgbe with MQ=0,0 and RSS=1,1
> > There are no luck with speed.
> >
> > [ 3] local xxx.xxx.185.135 port 5001 connected with yy.yy.74.11 port 5001
> > [ ID] Interval
