From: Simon Jeons <simon.jeons@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Hedi Berriche <hedi@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: page_alloc: Avoid marking zones full prematurely after zone_reclaim()
Date: Sun, 07 Apr 2013 14:37:16 +0800 [thread overview]
Message-ID: <5161141C.8030007@gmail.com> (raw)
In-Reply-To: <515E6FC4.5000202@gmail.com>
Ping!
On 04/05/2013 02:31 PM, Simon Jeons wrote:
> Hi Michal,
> On 03/21/2013 04:19 PM, Michal Hocko wrote:
>> On Thu 21-03-13 10:33:07, Simon Jeons wrote:
>>> Hi Mel,
>>> On 03/21/2013 02:19 AM, Mel Gorman wrote:
>>>> The following problem was reported against a distribution kernel when
>>>> zone_reclaim was enabled but the same problem applies to the mainline
>>>> kernel. The reproduction case was as follows
>>>>
>>>> 1. Run numactl -m +0 dd if=largefile of=/dev/null
>>>> This allocates a large number of clean pages in node 0
>>> I confuse why this need allocate a large number of clean pages?
>> It reads from file and puts pages into the page cache. The pages are not
>> modified so they are clean. Output file is /dev/null so no pages are
>> written. dd doesn't call fadvise(POSIX_FADV_DONTNEED) on the input file
>> by default so pages from the file stay in the page cache
>
> I try this in v3.9-rc5:
> dd if=/dev/sda of=/dev/null bs=1MB
> 14813+0 records in
> 14812+0 records out
> 14812000000 bytes (15 GB) copied, 105.988 s, 140 MB/s
>
> free -m -s 1
>
> total used free shared buffers
> cached
> Mem: 7912 1181 6731 0 663 239
> -/+ buffers/cache: 277 7634
> Swap: 8011 0 8011
>
> It seems that almost 15GB copied before I stop dd, but the used pages
> which I monitor during dd always around 1200MB. Weird, why?
>
--
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>
next prev parent reply other threads:[~2013-04-07 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 18:19 [PATCH] mm: page_alloc: Avoid marking zones full prematurely after zone_reclaim() Mel Gorman
2013-03-20 18:45 ` Michal Hocko
2013-03-21 2:32 ` Wanpeng Li
2013-03-21 2:32 ` Wanpeng Li
2013-03-21 2:33 ` Simon Jeons
2013-03-21 8:19 ` Michal Hocko
2013-03-21 8:32 ` Simon Jeons
2013-03-21 8:44 ` Michal Hocko
2013-03-21 8:59 ` Wanpeng Li
2013-03-21 8:59 ` Wanpeng Li
2013-04-05 6:31 ` Simon Jeons
2013-04-07 6:37 ` Simon Jeons [this message]
2013-04-09 10:05 ` Simon Jeons
2013-04-09 10:14 ` Michal Hocko
2013-04-09 10:20 ` Simon Jeons
2013-04-10 5:15 ` Ric Mason
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=5161141C.8030007@gmail.com \
--to=simon.jeons@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hedi@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).