From: Li Yu <raise.sail@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VM: Implements the swap-out page-clustering technique
Date: Mon, 08 Sep 2008 18:31:22 +0800 [thread overview]
Message-ID: <48C4FEFA.6070809@gmail.com> (raw)
In-Reply-To: <48C4FECF.2000708@gmail.com>
Li Yu 写道:
> hamidreza jahanjou 写道:
>> 2008/9/8, Li Yu <raise.sail@gmail.com>:
>>
>>> And the linear searching for whole address space of a vma is not good
>>> idea too, really.
>>>
>>>
>>>> + if (!page_allowed_in_cluster(cursor_page, ci))
>>>> + continue;
>>>>
>>>>
>>
>> Thank you for the review and comments. You are right in that searching
>> the whole process address space is not a good idea. The idea is to
>> make the scan range flexible, thus normally, assuming that the code
>> has been well-tuned, only a very limited number of VMA's are scanned.
>>
>> In general, i think that the cluster size and the scan range should be
>> tuned depending on the backing storage characteristics and the
>> low-on-memory severity. Like any VM code, this one needs tuning.
>>
>> BTW, the code could be implemented much more elegantly if the VMA's
>> were connected using a doubly-linked list. I wonder if there are
>> enought other codes with the same situation to justify making it
>> doubly-linked.
>>
>
> You are welcome!
>
> I think that scanning one vma each task is enough.
>
> The goal of swapoutclustering is to reduce disk heads movement while
> swapping in, it is based on space/time locality. I think that
> different vmas implied different using pattern, which also means they
> have different in program locality. Therefore, I think scanning multi
> vmas per task is not a good idea.
>
> Maybe, we need a page cache searching like for anonymous mapping
> instead of *linear* searching in each vma.
>
> I also have an uncompleted implementation for this feature ^_^
>
> Good luck.
>
next prev parent reply other threads:[~2008-09-08 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 12:04 [PATCH] VM: Implements the swap-out page-clustering technique Hamid R. Jahanjou
2008-09-04 23:14 ` Rik van Riel
2008-09-04 23:14 ` Andrew Morton
2008-09-05 7:45 ` Hamid R. Jahanjou
2008-09-05 6:58 ` Andrew Morton
2008-09-05 9:19 ` Andi Kleen
2008-09-05 20:27 ` Hamid R. Jahanjou
2008-09-05 19:45 ` Andi Kleen
2008-09-06 5:42 ` Rik van Riel
2008-09-08 0:28 ` Zan Lynx
2008-09-08 0:55 ` Rik van Riel
2008-09-10 8:16 ` Hamid R. Jahanjou
2008-09-10 17:08 ` Ray Lee
2008-09-10 17:39 ` Rik van Riel
2008-09-08 3:50 ` Li Yu
2008-09-08 9:51 ` hamidreza jahanjou
[not found] ` <48C4FECF.2000708@gmail.com>
2008-09-08 10:31 ` Li Yu [this message]
2008-09-24 13:56 ` Luiz Fernando N. Capitulino
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=48C4FEFA.6070809@gmail.com \
--to=raise.sail@gmail.com \
--cc=linux-kernel@vger.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 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.