From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Chanho Min <chanho.min@lge.com>
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
"'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: Tue, 25 Nov 2014 13:48:46 +0200 [thread overview]
Message-ID: <20141125114846.GA10150@node.dhcp.inet.fi> (raw)
In-Reply-To: <547465d2.0937460a.7739.fffff2baSMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 25, 2014 at 08:19:40PM +0900, Chanho Min 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.
>
> We are trying to solve two issues.
>
> We drop page caches by writing to /proc/sys/vm/drop_caches at specific point
> and make suspend-to-disk image. The size of this image is increased if faultaround
> is worked.
drop_caches should never be used outside debugging process. If you use it
as part of usual workflow you're doing something wrong.
I'm not aware about details on how suspend-to-disk works, but I don't see
much point in saving page cache pages into suspend-to-disk image. Dirty
pages should be write out and we can read them back after resume on first
use. Possible exception is mlocked pages.
> Under memory pressure, we want to drop many page caches as possible.
> But, The number of dropped pages are reduced compared to non-faultaround kernel.
The reason why you see more pages in page cache after drop_pages with
faultaround enabled is that drop_pages doesn't touch mapped pages. And
with faultaround we obviously have more pages mapped.
It's not a reason to have faultaround disable. You should take a closer
look on suspend process.
--
Kirill A. Shutemov
--
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: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Chanho Min <chanho.min@lge.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"'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: Tue, 25 Nov 2014 13:48:46 +0200 [thread overview]
Message-ID: <20141125114846.GA10150@node.dhcp.inet.fi> (raw)
In-Reply-To: <547465d2.0937460a.7739.fffff2baSMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 25, 2014 at 08:19:40PM +0900, Chanho Min 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.
>
> We are trying to solve two issues.
>
> We drop page caches by writing to /proc/sys/vm/drop_caches at specific point
> and make suspend-to-disk image. The size of this image is increased if faultaround
> is worked.
drop_caches should never be used outside debugging process. If you use it
as part of usual workflow you're doing something wrong.
I'm not aware about details on how suspend-to-disk works, but I don't see
much point in saving page cache pages into suspend-to-disk image. Dirty
pages should be write out and we can read them back after resume on first
use. Possible exception is mlocked pages.
> Under memory pressure, we want to drop many page caches as possible.
> But, The number of dropped pages are reduced compared to non-faultaround kernel.
The reason why you see more pages in page cache after drop_pages with
faultaround enabled is that drop_pages doesn't touch mapped pages. And
with faultaround we obviously have more pages mapped.
It's not a reason to have faultaround disable. You should take a closer
look on suspend process.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-11-25 11:48 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
2014-11-25 7:05 ` Andrew Morton
2014-11-25 11:19 ` Chanho Min
2014-11-25 11:48 ` Kirill A. Shutemov [this message]
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=20141125114846.GA10150@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=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.