From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>, Shaohua Li <shli@kernel.org>
Cc: linux-mm@kvack.org, hughd@google.com, riel@redhat.com
Subject: Re: [patch]mm: make madvise(MADV_WILLNEED) support swap file prefetch
Date: Tue, 8 Jan 2013 10:16:07 +0800 [thread overview]
Message-ID: <20130108021607.GA17766@hacker.(null)> (raw)
In-Reply-To: <20130107120630.82ba51ad.akpm@linux-foundation.org>
On Mon, Jan 07, 2013 at 12:06:30PM -0800, Andrew Morton wrote:
>On Mon, 7 Jan 2013 16:12:37 +0800
>Shaohua Li <shli@kernel.org> wrote:
>
>>
>> Make madvise(MADV_WILLNEED) support swap file prefetch. If memory is swapout,
>> this syscall can do swapin prefetch. It has no impact if the memory isn't
>> swapout.
>
>Seems sensible.
Hi Andrew and Shaohua,
What's the performance in the scenario of serious memory pressure? Since
in this case pages in swap are highly fragmented and cache hit is most
impossible. If WILLNEED path should add a check to skip readahead in
this case since swapin only leads to unnecessary memory allocation.
Regards,
Wanpeng Li
>
>> @@ -140,6 +219,18 @@ static long madvise_willneed(struct vm_a
>> {
>> struct file *file = vma->vm_file;
>>
>> +#ifdef CONFIG_SWAP
>
>It's odd that you put the ifdef in there, but then didn't test it!
>
>
>From: Andrew Morton <akpm@linux-foundation.org>
>Subject: mm-make-madvisemadv_willneed-support-swap-file-prefetch-fix
>
>fix CONFIG_SWAP=n build
>
>Cc: Shaohua Li <shli@fusionio.com>
>Cc: Hugh Dickins <hughd@google.com>
>Cc: Rik van Riel <riel@redhat.com>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>---
>
> mm/madvise.c | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff -puN mm/madvise.c~mm-make-madvisemadv_willneed-support-swap-file-prefetch-fix mm/madvise.c
>--- a/mm/madvise.c~mm-make-madvisemadv_willneed-support-swap-file-prefetch-fix
>+++ a/mm/madvise.c
>@@ -134,6 +134,7 @@ out:
> return error;
> }
>
>+#ifdef CONFIG_SWAP
> static int swapin_walk_pmd_entry(pmd_t *pmd, unsigned long start,
> unsigned long end, struct mm_walk *walk)
> {
>@@ -209,6 +210,7 @@ static void force_shm_swapin_readahead(s
>
> lru_add_drain(); /* Push any new pages onto the LRU now */
> }
>+#endif /* CONFIG_SWAP */
>
> /*
> * Schedule all required I/O operations. Do not wait for completion.
>_
>
>--
>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-01-08 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 8:12 Shaohua Li
2013-01-07 20:06 ` Andrew Morton
2013-01-08 2:16 ` Wanpeng Li [this message]
2013-01-08 2:16 ` Wanpeng Li
[not found] ` <50eb8180.6887320a.3f90.58b0SMTPIN_ADDED_BROKEN@mx.google.com>
2013-01-08 4:26 ` Shaohua Li
2013-01-08 5:38 ` Minchan Kim
2013-01-08 7:32 ` Shaohua Li
2013-01-08 7:54 ` Simon Jeons
2013-01-08 8:38 ` Minchan Kim
2013-01-08 9:13 ` Shaohua Li
2013-01-09 7:28 ` Minchan Kim
2013-01-08 8:45 ` Simon Jeons
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='20130108021607.GA17766@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
/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