public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erich Focht <efocht@ess.nec.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ia64 <linux-ia64@linuxia64.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH]: scheduler complex macros fixes
Date: Fri, 19 Jul 2002 19:11:48 +0200	[thread overview]
Message-ID: <200207191911.48427.efocht@ess.nec.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0207201855380.17169-100000@localhost.localdomain>

Hi Ingo,

On Saturday 20 July 2002 18:57, Ingo Molnar wrote:
> On Fri, 19 Jul 2002, Erich Focht wrote:
> > The attached patch fixes problems with the "complex" macros in the
> > scheduler, as discussed about a week ago with Ingo on this mailing list.
>
> the fix has been in my tree for some time, the latest version, against
> 2.5.26 is at:
>
>   http://people.redhat.com/mingo/O(1)-scheduler/sched-2.5.26-B7
>
> it has a number of other fixes as well, plus the SCHED_BATCH feature.
>
> 	Ingo

Thanks. But as long as SCHED_BATCH ins't in 2.5.X, we need this separate
fix. And if it's in the main tree, you don't need it additionally in
your patches. The fix is O(1) specific and I thought it should not hide
inside the SCHED_BATCH patches, some people might encounter these
problems...

Regards,
Erich


  reply	other threads:[~2002-07-19 17:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 14:55 [PATCH]: scheduler complex macros fixes Erich Focht
2002-07-20 16:57 ` Ingo Molnar
2002-07-19 17:11   ` Erich Focht [this message]
2002-07-20 17:16     ` Ingo Molnar
2002-07-19 17:28       ` Linus Torvalds
2002-07-19 14:54         ` mgross
2002-07-20 19:15           ` Ingo Molnar
2002-07-20 17:43         ` Ingo Molnar
2002-07-20 12:32           ` Erich Focht

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=200207191911.48427.efocht@ess.nec.de \
    --to=efocht@ess.nec.de \
    --cc=linux-ia64@linuxia64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.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