linux-ext4 - Re: [PATCH 1/2] fs-writeback: Add helper function to start writeback if idle

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: <4B2B9FF5.4030102@redhat.com>
Date:	Fri, 18 Dec 2009 09:29:57 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Jens Axboe <jens.axboe@...cle.com>
CC:	ext4 development <linux-ext4@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 1/2] fs-writeback: Add helper function to start	writeback
  if idle

Jens Axboe wrote:
> On Fri, Dec 11 2009, Eric Sandeen wrote:
>> ext4, at least, would like to start pushing on writeback if it starts
>> to get close to ENOSPC when reserving worst-case blocks for delalloc
>> writes.  Writing out delalloc data will convert those worst-case
>> predictions into usually smaller actual usage, freeing up space
>> before we hit ENOSPC based on this speculation.
>>
>> Thanks to Jens for the suggestion for the helper function,
>> & the naming help.
>>
>> I've made the helper return status on whether writeback was
>> started even though I don't plan to use it in the ext4 patch;
>> it seems like it would be potentially useful to test this
>> in some cases.
> 
> Eric, how do you want to merge these? I can easily take this first one
> through any branch, but I suppose the ext4 one should go through the
> proper ext4 channels.

Doesn't matter to me really; maybe it'd be simpler if it all went
though the ext4 tree so that there aren't any ordering problems?

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html