linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Jan Kara <jack@suse.cz>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] why does index in truncate_inode_pages_range() grows so much ?
Date: Fri, 13 Dec 2013 11:51:02 +0100	[thread overview]
Message-ID: <CAFLxGvy16wv0m4D+ydmqbksUu9CaEaDtGdtnk1YHa56jAU+SEA@mail.gmail.com> (raw)
In-Reply-To: <52AAD8D4.2060807@gmx.de>

On Fri, Dec 13, 2013 at 10:52 AM, Toralf Förster <toralf.foerster@gmx.de> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-12-13 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <529217CD.1000204@gmx.de>
     [not found] ` <20131203140214.GB31128@quack.suse.cz>
     [not found]   ` <529E3450.9000700@gmx.de>
2013-12-03 23:00     ` Jan Kara
2013-12-04 13:06       ` Jan Kara
2013-12-07 18:06         ` Toralf Förster
2013-12-11 20:26           ` Jan Kara
2013-12-13  9:52             ` Toralf Förster
2013-12-13 10:51               ` Richard Weinberger [this message]
2013-12-13 13:01                 ` [uml-devel] " Toralf Förster
2013-12-13 19:10                   ` Jan Kara
2013-12-05 23:23       ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFLxGvy16wv0m4D+ydmqbksUu9CaEaDtGdtnk1YHa56jAU+SEA@mail.gmail.com \
    --to=richard.weinberger@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=toralf.foerster@gmx.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox