lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1461089206.10638.226.camel@edumazet-glaptop3.roam.corp.google.com> Date: Tue, 19 Apr 2016 11:06:46 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Edward Cree <ecree@...arflare.com> Cc: netdev@...r.kernel.org, David Miller <davem@...emloft.net>, Jesper Dangaard Brouer <brouer@...hat.com>, linux-net-drivers@...arflare.com Subject: Re: [RFC PATCH net-next 7/8] net: ipv4: listified version of ip_rcv On Tue, 2016-04-19 at 17:50 +0100, Edward Cree wrote: > On 19/04/16 15:50, Eric Dumazet wrote: > > The main problem in UDP stack today is having to lock the socket because > > of the dumb forward allocation problem. > I'm not quite sure what you're referring to here, care to educate me? This was added for memory accounting, commit 95766fff6b9a78d11fc2d3812dd035381690b55d TCP stack does not reclaim its forward allocations as aggressively. (It has a concept of 'memory pressure')
Powered by blists - more mailing lists