Re: [uml-devel] why does index in truncate_inode_pages_range() growsso much ?

From: Richard Weinberger
Date: Fri Dec 13 2013 - 05:51:09 EST


On Fri, Dec 13, 2013 at 10:52 AM, Toralf Förster <toralf.foerster@xxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 12/11/2013 09:26 PM, Jan Kara wrote:
>> Thanks! So this works more or less as expected - trinity issued a
>> read at absurdly high offset so we created pagecache page a that
>> offset and tried to read data into it. That failed. We left the
>> page in the pagecache where it was for reclaim to reclaim it when
>> free pages are needed. Everything works as designed except we could
>> possibly argue that it's not the most efficient way to use
>> pages...
>>
>> Patch 'vfs: fix a bug when we do some dio reads with append dio
>> writes' (http://www.spinics.net/lists/linux-fsdevel/msg70899.html)
>> should actually change the situation and we won't unnecessarily
>> cache these pages.
>>
> confirmed - applied to latest git tree of Linus I helps.

Good to know! :-)

--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/