From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Izik Eidus <ieidus@redhat.com>
Cc: akpm@linux-foundation.org, hugh.dickins@tiscali.co.uk,
aarcange@redhat.com, chrisw@redhat.com, avi@redhat.com,
riel@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 10/10] ksm: change ksm nice level to be 5
Date: Mon, 20 Jul 2009 17:44:50 +0530 [thread overview]
Message-ID: <20090720121450.GG24157@balbir.in.ibm.com> (raw)
In-Reply-To: <4A645974.3020801@redhat.com>
* Izik Eidus <ieidus@redhat.com> [2009-07-20 14:48:04]:
> Balbir Singh wrote:
>> * Izik Eidus <ieidus@redhat.com> [2009-07-17 20:30:50]:
>>
>>
>>> From: Izik Eidus <ieidus@redhat.com>
>>>
>>> ksm should try not to disturb other tasks as much as possible.
>>>
>>> Signed-off-by: Izik Eidus <ieidus@redhat.com>
>>> ---
>>> mm/ksm.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/mm/ksm.c b/mm/ksm.c
>>> index 75d7802..4afe345 100644
>>> --- a/mm/ksm.c
>>> +++ b/mm/ksm.c
>>> @@ -1270,7 +1270,7 @@ static void ksm_do_scan(unsigned int scan_npages)
>>>
>>> static int ksm_scan_thread(void *nothing)
>>> {
>>> - set_user_nice(current, 0);
>>> + set_user_nice(current, 5);
>>>
>>
>> Is the 5 arbitrary? Why not +19? What is the intention of this change
>> - to run when no other task is ready to run?
>>
>
> Hey Balbir,
>
> I thought about giving it the lowest priority of nice before I did this
> patch, but then I came into understanding that it isn't right,
> Although ksm should not distrub other tasks while they are running, it
> does need to run while they are running,
> most of the use cases for ksm is to find identical pages in real time
> while they are changing in the application, so giving it the lowest
> priority doesn't seems right to me,
>
> But my understanding of how the nice prioritys are working is just my
> intuition, so if you know better and think that for the use case i
> described above other nice priority is better fit, tell me and I wont
> have any problem to change.
>
>
I was just checking to see why 5? May be it might be a good idea to
document or at-least have rules on what priorities kernel threads can
take?
>>
>>> while (!kthread_should_stop()) {
>>> if (ksm_run & KSM_RUN_MERGE) {
>>>
>>
>>
>
--
Balbir
--
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:[~2009-07-20 12:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 17:30 [PATCH 00/10] ksm resend Izik Eidus
2009-07-17 17:30 ` [PATCH 01/10] ksm: add mmu_notifier set_pte_at_notify() Izik Eidus
2009-07-17 17:30 ` [PATCH 02/10] ksm: first tidy up madvise_vma() Izik Eidus
2009-07-17 17:30 ` [PATCH 03/10] ksm: define MADV_MERGEABLE and MADV_UNMERGEABLE Izik Eidus
2009-07-17 17:30 ` [PATCH 04/10] ksm: the mm interface to ksm Izik Eidus
2009-07-17 17:30 ` [PATCH 05/10] ksm: no debug in page_dup_rmap() Izik Eidus
2009-07-17 17:30 ` [PATCH 06/10] ksm: identify PageKsm pages Izik Eidus
2009-07-17 17:30 ` [PATCH 07/10] ksm: Kernel SamePage Merging Izik Eidus
2009-07-17 17:30 ` [PATCH 08/10] ksm: prevent mremap move poisoning Izik Eidus
2009-07-17 17:30 ` [PATCH 09/10] ksm: change copyright message Izik Eidus
2009-07-17 17:30 ` [PATCH 10/10] ksm: change ksm nice level to be 5 Izik Eidus
2009-07-19 13:50 ` Hugh Dickins
2009-07-20 4:50 ` Balbir Singh
2009-07-20 11:48 ` Izik Eidus
2009-07-20 12:14 ` Balbir Singh [this message]
2009-07-20 18:38 ` Rik van Riel
2009-07-19 13:49 ` [PATCH 09/10] ksm: change copyright message Hugh Dickins
2009-07-20 18:37 ` Rik van Riel
2009-07-20 18:37 ` [PATCH 08/10] ksm: prevent mremap move poisoning Rik van Riel
2009-07-20 18:35 ` [PATCH 07/10] ksm: Kernel SamePage Merging Rik van Riel
2009-07-18 2:45 ` [PATCH 06/10] ksm: identify PageKsm pages Wu Fengguang
2009-07-20 18:32 ` Rik van Riel
2009-07-21 17:51 ` Andrea Arcangeli
2009-07-21 17:55 ` Rik van Riel
2009-07-21 18:01 ` Andrea Arcangeli
2009-07-21 18:17 ` Izik Eidus
2009-07-22 12:54 ` Hugh Dickins
2009-07-23 2:06 ` KAMEZAWA Hiroyuki
2009-07-23 11:43 ` Hugh Dickins
2009-07-23 11:49 ` Lee Schermerhorn
2009-07-22 12:45 ` Hugh Dickins
2009-07-22 16:52 ` Andrea Arcangeli
2009-07-23 11:36 ` Hugh Dickins
2009-07-20 18:11 ` [PATCH 05/10] ksm: no debug in page_dup_rmap() Rik van Riel
2009-07-21 7:16 ` Nick Piggin
2009-07-20 17:38 ` [PATCH 04/10] ksm: the mm interface to ksm Rik van Riel
2009-07-20 15:09 ` [PATCH 03/10] ksm: define MADV_MERGEABLE and MADV_UNMERGEABLE Rik van Riel
2009-07-20 15:44 ` Ralf Baechle
2009-07-20 15:05 ` [PATCH 02/10] ksm: first tidy up madvise_vma() Rik van Riel
2009-07-20 14:48 ` [PATCH 01/10] ksm: add mmu_notifier set_pte_at_notify() Rik van Riel
2009-07-21 17:59 ` [PATCH 00/10] ksm resend Andrea Arcangeli
2009-07-22 13:05 ` Hugh Dickins
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=20090720121450.GG24157@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ieidus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.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 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).