public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Will Lentz <will_lentz@trimble.com>,
	ecos <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] more scheduling priorities
Date: Mon, 11 Jul 2005 08:33:00 -0000	[thread overview]
Message-ID: <m3mzothhe8.fsf@xl5.calivar.com> (raw)
In-Reply-To: <20050711071528.GB15048@lunn.ch>

Andrew Lunn <andrew@lunn.ch> writes:

> On Sun, Jul 10, 2005 at 03:03:44PM -0700, Will Lentz wrote:
> > Hi,
> > 
> > Is it possible to get Nick's patch adding more scheduling priorities
> > applied to CVS?  or maybe just put a link to this patch somewhere?
> > http://sourceware.org/ml/ecos-discuss/2003-03/msg00362.html

You could try applying that patch and see what happens. It may need a
little editing to get it to apply cleanly, but not much has happened
in that code for some time, so it should be too difficult.

> 
> That would be for Nick to decide.

As the message says, this is potentially a destabilizing change to the
scheduler. It really needs some intensive testing, and maybe even some
specific test programs written to exercise it. I'm also not very happy
with the choice of names used here, and the fact that several
assertion tests become impossible, and would like to rewrite it a
little before committing it.

-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2005-07-11  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 22:03 Will Lentz
2005-07-11  7:15 ` Andrew Lunn
2005-07-11  8:33   ` Nick Garnett [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=m3mzothhe8.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=will_lentz@trimble.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 read-only IMAP folder(s) and NNTP newsgroup(s).