linux-kernel - Re: [PATCH 08/19] ceph: address space operations

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090723191611.GE19207@basil.fritz.box>
Date:	Thu, 23 Jul 2009 21:16:11 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Sage Weil <sage@...dream.net>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/19] ceph: address space operations

> There are two other memory allocations during writeout: a vector of pages 
> to be written, and the message we're sending to the OSD.  If I use a 
> mempool for those to guarantee as least some writeout will occur, how do I 
> safely defer when allocations do fail?  Will pdflush (or it's replacement) 
> eventually come back and try ->writepages() again?

mempool allocs should never fail, just block for a long time until
someone else frees. This means you need to ensure of course you
always make forward progress.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/