From: Robert Hancock <hancockrwd@gmail.com>
To: kernel mailz <kernelmailz@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slowing down the schedular, How?
Date: Thu, 25 Jun 2009 17:40:56 -0600 [thread overview]
Message-ID: <4A440B08.6050006@gmail.com> (raw)
In-Reply-To: <abe8a1fd0906251136t36d78428k90a610fdff987ab6@mail.gmail.com>
On 06/25/2009 12:36 PM, kernel mailz wrote:
> Hi,
>
> I have a SMP linux running on 85xx poweprc. Say on Core 0 and Core 1
> two different processes are running and on both the schedular runs.
> Now for some special case, if one of my process issues a ioctl which
> gets serviced by a kernel module, I wish to slow the schedular on that
> core only. Otherwise the performance will get degraded.
>
> Should I use highest priority tasklet, will it be sufficient or i need
> to do something special
>
> -TZ
Not clear what you mean by "slowing the scheduler" or "performance will
get degraded". The scheduler is not a process, it runs when something
triggers it to run.
prev parent reply other threads:[~2009-06-25 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 18:36 Slowing down the schedular, How? kernel mailz
2009-06-25 18:38 ` kernel mailz
2009-06-25 23:40 ` Robert Hancock [this message]
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=4A440B08.6050006@gmail.com \
--to=hancockrwd@gmail.com \
--cc=kernelmailz@googlemail.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.