From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>, 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: Thu, 21 Mar 2013 16:59:24 +0800 [thread overview]
Message-ID: <20130321085924.GA13665@hacker.(null)> (raw)
In-Reply-To: <514AC583.2090909@gmail.com>
On Thu, Mar 21, 2013 at 04:32:03PM +0800, 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
>
>Thanks for your clarify Michal.
>dd will use page cache instead of direct IO? Where can I got dd
>source codes?
>One offline question, when should use page cache and when should use
>direct IO?
who prefer direct IO:
- the users believe they can manage caching of file contents better than
the kernel can.
- the users want to avoid overflowing the page cache with data which is
unlikely to be of use in the near future.
Regards,
Wanpeng Li
>
>
>--
>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>
next prev parent reply other threads:[~2013-03-21 8:59 UTC|newest]
Thread overview: 28+ 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:19 ` Mel Gorman
2013-03-20 18:45 ` Michal Hocko
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 2:33 ` Simon Jeons
2013-03-21 8:19 ` Michal Hocko
2013-03-21 8:19 ` Michal Hocko
2013-03-21 8:32 ` Simon Jeons
2013-03-21 8:32 ` Simon Jeons
2013-03-21 8:44 ` Michal Hocko
2013-03-21 8:44 ` Michal Hocko
2013-03-21 8:59 ` Wanpeng Li [this message]
2013-03-21 8:59 ` Wanpeng Li
2013-04-05 6:31 ` Simon Jeons
2013-04-05 6:31 ` Simon Jeons
2013-04-07 6:37 ` Simon Jeons
2013-04-07 6:37 ` Simon Jeons
2013-04-09 10:05 ` Simon Jeons
2013-04-09 10:05 ` Simon Jeons
2013-04-09 10:14 ` Michal Hocko
2013-04-09 10:14 ` Michal Hocko
2013-04-09 10:20 ` Simon Jeons
2013-04-09 10:20 ` Simon Jeons
2013-04-10 5:15 ` Ric Mason
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='20130321085924.GA13665@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.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 \
--cc=simon.jeons@gmail.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.