| 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: <BANLkTim0MNgqeh1KTfvpVFuAvebKyQV8Hg@mail.gmail.com> Date: Tue, 26 Apr 2011 14:07:17 +0800 From: Dave Young <hidave.darkstar@...il.com> To: Wu Fengguang <fengguang.wu@...el.com> Cc: linux-mm <linux-mm@...ck.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: readahead and oom On Tue, Apr 26, 2011 at 2:05 PM, Dave Young <hidave.darkstar@...il.com> wrote: > On Tue, Apr 26, 2011 at 1:55 PM, Wu Fengguang <fengguang.wu@...el.com> wrote: >> On Tue, Apr 26, 2011 at 01:49:25PM +0800, Dave Young wrote: >>> Hi, >>> >>> When memory pressure is high, readahead could cause oom killing. >>> IMHO we should stop readaheading under such circumstances。If it's true >>> how to fix it? >> >> Good question. Before OOM there will be readahead thrashings, which >> can be addressed by this patch: >> >> http://lkml.org/lkml/2010/2/2/229 > > Hi, I'm not clear about the patch, could be regard as below cases? > 1) readahead alloc fail due to low memory such as other large allocation For example vm balloon allocate lots of memory, then readahead could fail immediately and then oom > 2) readahead thrashing caused by itself > >> >> However there seems no much interest on that feature.. I can separate >> that out and resubmit it standalone if necessary. >> >> Thanks, >> Fengguang >> > > > > -- > Regards > dave > -- Regards dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists