Hello netdev,
we see a performance drop (about ~30%) on sfc driver (SFC9020) when
performing netperf TCP maerts test. It seems it started from 4.7-rc0.
Which commit/change could cause this regression? Any hints?
I opened a bugzilla [0] where you can find images with results.
[0]
> On Wed, Apr 27, 2016 at 2:36 AM, Otto Sabart <osab...@redhat.com> wrote:
> >
> > Hello everyone,
> > does anybody have a problem with LRO on ixge (on latest 4.6-rc5)?
> > I cannot find a way to enable it.
> >
> > On stable RHEL7.2 kernel everything
Hello everyone,
does anybody have a problem with LRO on ixge (on latest 4.6-rc5)?
I cannot find a way to enable it.
On stable RHEL7.2 kernel everything works fine.
I opened a bug report [0].
[0] https://bugzilla.kernel.org/show_bug.cgi?id=117291
Thanks!
Ota
signature.asc
Description: PGP
Hi Rick,
> *) It is good to be binding netperf and netserver - helps with
> reproducibility, but why the two -T options? A brief look at src/netsh.c
> suggests it will indeed set the two binding options separately but that is
> merely a side-effect of how I wrote the code. It wasn't an
> Hi Ota,
>
> It looks like there were a few changes that went through that could be
> causing the regression. The most obvious one that jumps out at me is commit
> 72bfd32d2f84 ("ixgbe: disable LRO by default"). As such one thing you might
> try doing is turning on LRO support via ethtool -k
Hello netdev,
I probably found a performance regression on ixgbe (Intel 82599EB
10-Gigabit NIC) on v4.4-rc3. I am able to see this problem since
v4.4-rc1.
The bug report you can find here [0].
Can somebody take a look at it?
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1288124
thanks,
Ota
Thank you Ariel, just let me know if you find anything.
On 23. Oct (Friday) v 08:16:01 + 2015, Ariel Elior wrote:
> Looking into it...
>
> > Hello netdev,
> > I probably found a bug in kernel-4.3.0-0.rc5 (bnx2x driver). So I opened
> > new bug report in our bugzilla [0]. Michal Schmidt told
Hello netdev,
I probably found a bug in kernel-4.3.0-0.rc5 (bnx2x driver). So I opened
new bug report in our bugzilla [0]. Michal Schmidt told me the best way
to solve an upstream bug is to contact you directly to netdev list.. so
here I am :).
Can somebody take a look at it?
[0]