From: Andrew Morton <akpm@linux-foundation.org>
To: Chanho Min <chanho.min@lge.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>, Michal Hocko <mhocko@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
HyoJun Im <hyojun.im@lge.com>, Gunho Lee <gunho.lee@lge.com>,
Wonhong Kwon <wonhong.kwon@lge.com>
Subject: Re: [PATCH] mm: add parameter to disable faultaround
Date: Mon, 24 Nov 2014 23:05:02 -0800 [thread overview]
Message-ID: <20141124230502.30f9b6f0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1416898318-17409-1-git-send-email-chanho.min@lge.com>
On Tue, 25 Nov 2014 15:51:58 +0900 Chanho Min <chanho.min@lge.com> wrote:
> The faultaround improves the file read performance, whereas pages which
> can be dropped by drop_caches are reduced. On some systems, The amount of
> freeable pages under memory pressure is more important than read
> performance.
The faultaround pages *are* freeable. Perhaps you meant "free" here.
Please tell us a great deal about the problem which you are trying to
solve. What sort of system, what sort of workload, what is bad about
the behaviour which you are observing, etc.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Chanho Min <chanho.min@lge.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>, Michal Hocko <mhocko@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
HyoJun Im <hyojun.im@lge.com>, Gunho Lee <gunho.lee@lge.com>,
Wonhong Kwon <wonhong.kwon@lge.com>
Subject: Re: [PATCH] mm: add parameter to disable faultaround
Date: Mon, 24 Nov 2014 23:05:02 -0800 [thread overview]
Message-ID: <20141124230502.30f9b6f0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1416898318-17409-1-git-send-email-chanho.min@lge.com>
On Tue, 25 Nov 2014 15:51:58 +0900 Chanho Min <chanho.min@lge.com> wrote:
> The faultaround improves the file read performance, whereas pages which
> can be dropped by drop_caches are reduced. On some systems, The amount of
> freeable pages under memory pressure is more important than read
> performance.
The faultaround pages *are* freeable. Perhaps you meant "free" here.
Please tell us a great deal about the problem which you are trying to
solve. What sort of system, what sort of workload, what is bad about
the behaviour which you are observing, etc.
next prev parent reply other threads:[~2014-11-25 7:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 6:51 [PATCH] mm: add parameter to disable faultaround Chanho Min
2014-11-25 6:51 ` Chanho Min
2014-11-25 7:05 ` Andrew Morton [this message]
2014-11-25 7:05 ` Andrew Morton
2014-11-25 11:19 ` Chanho Min
2014-11-25 11:48 ` Kirill A. Shutemov
2014-11-25 11:48 ` Kirill A. Shutemov
[not found] ` <547465d2.6561420a.04ed.0514SMTPIN_ADDED_BROKEN@mx.google.com>
2014-11-25 11:40 ` Andrew Morton
2014-11-25 11:40 ` Andrew Morton
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=20141124230502.30f9b6f0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chanho.min@lge.com \
--cc=gunho.lee@lge.com \
--cc=hughd@google.com \
--cc=hyojun.im@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=wonhong.kwon@lge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.