All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Maciej Soltysiak <solt2@dns.toxicfilms.tv>, linux-kernel@vger.kernel.org
Subject: Re: Trying out SCHED_BATCH
Date: Wed, 29 Dec 2004 23:46:27 +0100	[thread overview]
Message-ID: <4d8e3fd304122914466b42c632@mail.gmail.com> (raw)
In-Reply-To: <41D31373.1090801@kolivas.org>

On Thu, 30 Dec 2004 07:28:35 +1100, Con Kolivas <kernel@kolivas.org> wrote:
> Maciej Soltysiak wrote:
> > Hi
> >
> > Con wrote:
> >
> >> Only the staircase scheduler currently has an implementation of
> >> sched_batch and you need 2 more patches on top of the staircase patch
> >> for it to work.
> >
> > Hmm, Is it feasable to write a sched_batch policy for the current linux
> > schedulers?
> 
> Yes.
> 
> The proper way to make a sched_batch implementation is more
> comprehensive than what is made for staircase to prevent a deadlock
> based on a batch task getting an important lock in the kernel and not
> being able to release it due to a sched_normal task being higher
> priority than it that is actually trying to get the lock. There is code
> in the staircase version to prevent this from happening but probably not
> complete enough in design to prevent everything. However it works and I
> haven't had any reports of lockups since I implemented the extra checking.
> 
> Would you like me to create a version like that? I don't have the time
> to try and make a more comprehensive solution and follow the debugging
> of such a beast.
> 
> > I mean, if there are people that want it bad, maybe it would be nice to
> > be able
> > to use a version of sched_batch that would work without the staircase
> > scheduler.
> > It is still experimental, right?
> 
> No it's not experimental. It is very stable and used in production systems.

Are you gointo  to push to Linus/Andrew ?

-- 
Paolo

  reply	other threads:[~2004-12-29 22:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25 11:31 Trying out SCHED_BATCH Rajsekar
2004-12-25 11:41 ` Con Kolivas
2004-12-29 20:14   ` Maciej Soltysiak
2004-12-29 20:28     ` Con Kolivas
2004-12-29 22:46       ` Paolo Ciarrocchi [this message]
2004-12-29 22:56         ` Con Kolivas
2004-12-30  7:12           ` Paolo Ciarrocchi
2004-12-30  7:20             ` Andrew Morton
2004-12-30  7:36               ` Paolo Ciarrocchi
2004-12-30  7:41                 ` Con Kolivas
2004-12-30 16:16               ` Bill Davidsen
2005-01-02  0:26                 ` Peter Williams
2004-12-25 11:46 ` Matan Peled
2004-12-25 18:45 ` Bill Davidsen
2004-12-25 23:09   ` Con Kolivas

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=4d8e3fd304122914466b42c632@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solt2@dns.toxicfilms.tv \
    /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.