| Message ID | 20220614163024.1061106-1-eric.dumazet@gmail.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | tcp: final (?) round of mem pressure fixes | expand |
On Tue, Jun 14, 2022 at 9:30 AM Eric Dumazet <eric.dumazet@gmail.com> wrote: > > From: Eric Dumazet <edumazet@google.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 >
From: Eric Dumazet <edumazet@google.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. 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(-)