From: Namhyung Kim <namhyung@kernel.org>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: changing timeslice in linux
Date: Tue, 21 Aug 2012 09:16:50 +0900 [thread overview]
Message-ID: <87mx1phzf1.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CALKntY0dQFxmSz+61Bia-zxpvsQg7kySG1mfk1GVc90YCc27qw@mail.gmail.com> (Xin Tong's message of "Mon, 20 Aug 2012 07:51:52 -0700")
On Mon, 20 Aug 2012 07:51:52 -0700, Xin Tong wrote:
> On Sun, Aug 19, 2012 at 10:54 PM, Mike Galbraith <efault@gmx.de> wrote:
>> On Sun, 2012-08-19 at 11:58 -0700, Xin Tong wrote:
>>> I have 2 questions about linux 2.6 x86_64 scheduler.
>>>
>>> 1. is the default scheduling algorithm SCHED_NORMAL in linux ?
>>
>> Yes.
> Is there any document describing what the sched_normal is ? it is more
> difficult than SCHED_RR to infer its meaning just based on its name ?
>>
>>> 2. how do i change the time slice in linux source code ?
>>
>> You shouldn't need to. You can tune "slice" by adjusting
>> sched_latency_ns and sched_min_granularity_ns, but note that "slice" is
>> not a fixed quantum. Also note that CFS preemption decisions are based
>> upon instantaneous state. A task may have received a full (variable)
>> "slice" of CPU time, but preemption will be triggered only if a more
>> deserving task is available, so a "slice" is not the "max uninterrupted
>> CPU time" that you may expect it to be.. but it is somewhat similar.
>>
>> -Mike
>>
> This can be done without recompiling and reinstalling the kernel ?
> maybe one simply needs to write to a device file under /dev ?
You can find those files under /proc/sys/kernel/.
Thanks,
Namhyung
next prev parent reply other threads:[~2012-08-21 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 18:58 Xin Tong
2012-08-20 5:54 ` Mike Galbraith
2012-08-20 14:51 ` Xin Tong
2012-08-21 0:16 ` Namhyung Kim [this message]
2012-08-28 20:15 ` Xin Tong
2012-08-28 20:16 ` Xin Tong
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=87mx1phzf1.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xerox.time.tech@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome