[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89i+ReVNn93+EvQ1PvctEAy9uEQUDQgTpRUNhCiAuqNLxaw@mail.gmail.com>
Date: Wed, 15 Jun 2022 23:07:17 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: David Miller <davem@...emloft.net>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
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 v2 net-next 0/2] tcp: final (?) round of mem pressure fixes
On Wed, Jun 15, 2022 at 11:00 PM Eric Dumazet <edumazet@...gle.com> wrote:
>
> On Wed, Jun 15, 2022 at 4:56 AM David Miller <davem@...emloft.net> wrote:
> >
> > From: Eric Dumazet <eric.dumazet@...il.com>
> > Date: Tue, 14 Jun 2022 10:17:32 -0700
> >
> > > 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.
> > >
> > > v2: deal with zerocopy tx paths.
> >
> > Does not apply cleanly to net, please respin.
> >
> > Thank you.
>
> I was targeting net-next tree for this old bug, and planning to
> prepare stable backports.
This was because in net-next we got rid of SK_MEM_QUANTUM, and to
limit merge conflicts.
>
> Tell me if you prefer to respin to net tree, probably later today
> because I am traveling.
>
> Thanks.
Powered by blists - more mailing lists