linux-kernel - Re: [PATCH 00/19] periodic write-back timer optimization

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] [day] [month] [year] [list]

Message-ID: <4A265AF7.5000101@nokia.com>
Date:	Wed, 03 Jun 2009 14:13:59 +0300
From:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
To:	Jens Axboe <jens.axboe@...cle.com>,
	Christoph Hellwig <hch@...radead.org>,
	"viro@...IV.linux.org.uk" <viro@...IV.linux.org.uk>
CC:	Arnd Bergmann <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 00/19] periodic write-back timer optimization

Jens Axboe wrote:
> On Thu, May 28 2009, Artem Bityutskiy wrote:
>> Jens Axboe wrote:
>>> That would be great, I would have no problem integrating such a feature.
>>> It definitely makes sense.
>> Hi Al, Christoph,
>>
>> unless you have objections against the whole idea, I wonder if
>> it would be possible to make the patches which wrap sb->s_dirt
>> usage go via VFS tree first, and then I'd continue the timer
>> optimization work separately. IMO, wrapping s_dirt makes sense
>> in general. I mean, patches 01-17 from this series.
> 
> That makese sense, those are totally separate from the actual
> functionality.

Reminding ping.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
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/