On 2017.02.06 at 19:12 -0200, Marcelo Ricardo Leitner wrote:
> On Fri, Feb 03, 2017 at 06:47:33AM -0800, Eric Dumazet wrote:
> > On Fri, 2017-02-03 at 12:28 -0200, Marcelo Ricardo Leitner wrote:
> >
> > > Aren't you mixing the endpoints here? MSS is the largest amount of data
> > > that the peer c
On 2017.02.06 at 19:12 -0200, Marcelo Ricardo Leitner wrote:
> On Fri, Feb 03, 2017 at 06:47:33AM -0800, Eric Dumazet wrote:
> > On Fri, 2017-02-03 at 12:28 -0200, Marcelo Ricardo Leitner wrote:
> >
> > > Aren't you mixing the endpoints here? MSS is the largest amount of data
> > > that the peer c
On 2017.02.03 at 09:54 -0200, Marcelo Ricardo Leitner wrote:
> On Thu, Feb 02, 2017 at 05:59:24AM -0800, Eric Dumazet wrote:
> > On Thu, 2017-02-02 at 05:31 -0800, Eric Dumazet wrote:
> >
> > > Anyway, I suspect the test is simply buggy ;)
> > >
> > > diff --git a/net/ipv4/tcp_input.c b/net/ipv4/
On 2017.02.02 at 04:32 -0800, Eric Dumazet wrote:
> On Thu, 2017-02-02 at 12:52 +0100, Markus Trippelsdorf wrote:
> > Hi,
> >
> > from time to time I see the following warning in my kernel log:
> >
> > TCP: eth0: Driver has suspect GRO implementation, TCP pe
Hi,
from time to time I see the following warning in my kernel log:
TCP: eth0: Driver has suspect GRO implementation, TCP performance may be
compromised.
This happens although I run "/usr/sbin/ethtool -K eth0 gro off" in my
local boot script.
What is the warning trying to tell me?
--
Markus
On 2016.10.14 at 09:43 +0200, Eric Dumazet wrote:
> On Fri, 2016-10-14 at 09:33 +0200, Markus Trippelsdorf wrote:
> > While playing with BBR I noticed that it was missing in the list of
> > possible config DEFAULT_TCP_CONG choices. Fixed thusly.
> >
> > Signed-
While playing with BBR I noticed that it was missing in the list of
possible config DEFAULT_TCP_CONG choices. Fixed thusly.
Signed-off-by: Markus Trippelsdorf
diff --git a/net/ipv4/Kconfig b/net/ipv4/Kconfig
index 300b06888fdf..b54b3ca939db 100644
--- a/net/ipv4/Kconfig
+++ b/net/ipv4/Kconfig
On 2016.10.13 at 08:02 +0200, Markus Trippelsdorf wrote:
> On 2016.10.11 at 04:57 -0400, David Miller wrote:
> > From: Linus Torvalds
> > Date: Mon, 10 Oct 2016 22:47:50 -0700
> >
> > > On Mon, Oct 10, 2016 at 10:39 PM, Linus Torvalds
> > > wrote:
>
On 2016.10.12 at 23:18 -0700, Linus Torvalds wrote:
> On Oct 12, 2016 23:07, "Markus Trippelsdorf" wrote:
> >
> > This is nf_register_net_hook at net/netfilter/core.c:106
>
> The "*regs" access?
Yeah.
105 entry->orig_ops = reg;
106 ent
On 2016.10.11 at 04:57 -0400, David Miller wrote:
> From: Linus Torvalds
> Date: Mon, 10 Oct 2016 22:47:50 -0700
>
> > On Mon, Oct 10, 2016 at 10:39 PM, Linus Torvalds
> > wrote:
> >>
> >> I guess I will have to double-check that the slub corruption is gone
> >> still with that fixed.
> >
> > S
On 2015.09.18 at 16:42 +, Chris Snook wrote:
> I think atl1e is the victim here, not the cause. It's probably the last
> device being brought up that wants to use the swiotlb, so you haven't seen
> other devices failing for the same reason. Can you post your dmesg or boot
> log from both a boot
On 2015.09.12 at 08:51 +0200, Markus Trippelsdorf wrote:
> With the current Linus git tree I get an occasional swiotlb allocation
> error during network setup at boot-time:
>
> ATL1E :02:00.0: swiotlb buffer is full (sz: 529461 bytes)
> swiotlb: coherent allocation failed for
With the current Linus git tree I get an occasional swiotlb allocation
error during network setup at boot-time:
ATL1E :02:00.0: swiotlb buffer is full (sz: 529461 bytes)
swiotlb: coherent allocation failed for device :02:00.0 size=529461
CPU: 0 PID: 200 Comm: ifconfig Not tainted 4.2.0-
commit bea3348eef27e6044b6161fd04c3152215f96411 :
[NET]: Make NAPI polling independent of struct net_device objects.
causes my machine to hang on shutdown. The following patch fixes the
problem for me.
Signed-off-by: Markus Trippelsdorf <[EMAIL PROTECTED]>
diff --git a/drivers/net/r81
14 matches
Mail list logo
