linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Roman Gushchin <klamm@yandex-team.ru>
To: Simon Jeons <simon.jeons@gmail.com>, Eric Wong <normalperson@yhbt.net>
Cc: xtu4 <xiaobing.tu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tip-commits@vger.kernel.org"
	<linux-tip-commits@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"di.zhang@intel.com" <di.zhang@intel.com>
Subject: Re: resend--[PATCH]  improve read ahead in kernel
Date: Thu, 20 Dec 2012 14:55:18 +0400	[thread overview]
Message-ID: <1461356000918@webcorp1g.yandex-team.ru> (raw)
In-Reply-To: <1355984435.1374.3.camel@kernel-VirtualBox>

Hi Simon,

20.12.2012, 10:21, "Simon Jeons" <simon.jeons@gmail.com>:
> On Sun, 2012-12-16 at 02:15 +0000, Eric Wong wrote:
>
>> ?xtu4 <xiaobing.tu@intel.com> wrote:
>>> ?resend it, due to format error
>>>
>>> ?Subject: [PATCH] when system in low memory scenario, imaging there is a mp3
>>> ??play, ora video play, we need to read mp3 or video file
>>> ??from memory to page cache,but when system lack of memory,
>>> ??page cache of mp3 or video file will be reclaimed.once read
>>> ??in memory, then reclaimed, it will cause audio or video
>>> ??glitch,and it will increase the io operation at the same
>>> ??time.
>> ?To me, this basically describes how POSIX_FADV_NOREUSE should work.
>
> Hi Eric,
>
> But why fadvise POSIX_FADV_NOREUSE almost do nothing? Why not set some
> flag or other things for these use once data?

Because, it's not clear how should it work in some cases.
Do we expect one access? Should we track a page as accessed after any access (even if only one byte was read)?
What should we do with already-cached pages? etc.

IMHO, it will be better to introduce something like POSIX_FADV_DONTCACHE.
Corresponding pages can be added (ratated) to the tail of the inactive LRU after copying data in read() internals,
or after minor/major pagefault.

>
>> ?I would like to have this ability via fadvise (and not CONFIG_).
>>
>> ?Also, I think your patch has too many #ifdefs to be accepted.
>>
>> ?--
>> ?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>
>
> --
> 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>

--
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:[~2012-12-20 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 15:57 [PATCH] " xtu4
2012-12-09 10:18 ` Randy Dunlap
2012-12-11  3:40 ` resend--[PATCH] " xtu4
2012-12-16  2:15   ` Eric Wong
2012-12-20  6:20     ` Simon Jeons
2012-12-20 10:55       ` Roman Gushchin [this message]

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=1461356000918@webcorp1g.yandex-team.ru \
    --to=klamm@yandex-team.ru \
    --cc=di.zhang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=simon.jeons@gmail.com \
    --cc=xiaobing.tu@intel.com \
    /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