[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iJLo7C4hLmOQ9dQ=_RG5xx3JJSYWoyC9XoBMVFu7QHJ-w@mail.gmail.com>
Date: Tue, 14 Jun 2022 09:50:15 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
netdev <netdev@...r.kernel.org>,
Soheil Hassas Yeganeh <soheil@...gle.com>,
Wei Wang <weiwan@...gle.com>,
Shakeel Butt <shakeelb@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>
Subject: Re: [PATCH net-next 0/2] tcp: final (?) round of mem pressure fixes
On Tue, Jun 14, 2022 at 9:30 AM Eric Dumazet <eric.dumazet@...il.com> wrote:
>
> From: Eric Dumazet <edumazet@...gle.com>
>
> While working on prior patch series (e10b02ee5b6c "Merge branch
> 'net-reduce-tcp_memory_allocated-inflation'"), I found that we
> could still have frozen TCP flows under memory pressure.
>
> I thought we had solved this in 2015, but the fix was not complete.
>
I will send a V2, because we need to deal with tx zero copy paths.
> Eric Dumazet (2):
> tcp: fix over estimation in sk_forced_mem_schedule()
> tcp: fix possible freeze in tx path under memory pressure
>
> net/ipv4/tcp.c | 18 ++++++++++++++++--
> net/ipv4/tcp_output.c | 7 ++++---
> 2 files changed, 20 insertions(+), 5 deletions(-)
>
> --
> 2.36.1.476.g0c4daa206d-goog
>
Powered by blists - more mailing lists