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
| ||
|
Date: Thu, 18 Jun 2015 07:35:53 -0700 From: Eric Dumazet <edumazet@...gle.com> To: Michal Hocko <mhocko@...e.cz> Cc: David Rientjes <rientjes@...gle.com>, Vlastimil Babka <vbabka@...e.cz>, Shaohua Li <shli@...com>, netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>, kernel-team <Kernel-team@...com>, clm@...com, linux-mm@...ck.org, dbavatar@...il.com Subject: Re: [RFC V3] net: don't wait for order-3 page allocation On Thu, Jun 18, 2015 at 7:30 AM, Michal Hocko <mhocko@...e.cz> wrote: > Abusing __GFP_NO_KSWAPD is a wrong way to go IMHO. It is true that the > _current_ implementation of the allocator has this nasty and very subtle > side effect but that doesn't mean it should be abused outside of the mm > proper. Why shouldn't this path wake the kswapd and let it compact > memory on the background to increase the success rate for the later > high order allocations? I kind of agree. If kswapd is a problem (is it ???) we should fix it, instead of adding yet another flag to some random locations attempting memory allocations. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists