public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: mingo@elte.hu
Cc: Mike Kravetz <kravetz@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] current scheduler bits, 2.5.21
Date: 10 Jun 2002 17:27:35 -0700	[thread overview]
Message-ID: <1023755255.21155.166.camel@sinai> (raw)
In-Reply-To: <Pine.LNX.4.44.0206110134130.5377-100000@elte.hu>

On Mon, 2002-06-10 at 17:05, Ingo Molnar wrote:

> Thanks. I've applied your patch with the following additional
> improvements:
> 
> - The spin_unlock_irqrestore path does not have to be split up like the
>   spin_lock path: spin_unlock() + local_irq_restore() ==
>   spin_unlock_irqrestore() ... this is true both in task_rq_unlock() and
>   rq_unlock() code.

I know.  The reason I split them up is to maintain consistency through
the way we lock vs unlock and enable vs disable interrupts.  Partly for
style, partly in case we ever decide to hook the different calls in a
different manner.

I do not see this in your patch, though ...

> - in sys_sched_yield() you removed an optimization: the final spin_unlock
>   does not have to check for resched explicitly, we'll call into
>   schedule() anyway. I've introduced a new spin_unlock variant:
>   spin_unlock_no_resched(), which uses preempt_enable_no_resched().

Ah yes, very good.  I was too busy noticing the optimization I _did_ put
in: not calling rq_unlock here as we can just leave interrupts disabled
on return...

Very good.

> otherwise it's looking good. The attached patch is my current tree which
> includes the rq-lock/unlock optimization plus the previous patches
> (race-fix and sync-wakeup), against 2.5.21-vanilla.

Excellent.

	Robert Love


  reply	other threads:[~2002-06-11  0:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 23:20 Scheduler Bug (set_cpus_allowed) Mike Kravetz
2002-06-07 18:36 ` Robert Love
2002-06-07 19:12   ` Mike Kravetz
2002-06-10 20:12     ` Ingo Molnar
2002-06-10 20:57       ` Mike Kravetz
2002-06-10 22:35         ` Ingo Molnar
2002-06-10 23:15           ` Mike Kravetz
2002-06-10 23:24             ` Ingo Molnar
2002-06-10 23:28               ` Robert Love
2002-06-11  0:05                 ` [patch] current scheduler bits, 2.5.21 Ingo Molnar
2002-06-11  0:27                   ` Robert Love [this message]
2002-06-11 17:35                     ` [patch] current scheduler bits #2, 2.5.21 Ingo Molnar
2002-06-11 18:25                       ` Robert Love
2002-06-11 18:33                         ` [patch] current scheduler bits #3, 2.5.21 Ingo Molnar
2002-06-13 21:26                           ` [PATCH] " Robert Love
2002-06-13 22:06                             ` [patch] current scheduler bits #4, 2.5.21 Ingo Molnar
2002-06-07 23:20   ` Scheduler Bug (set_cpus_allowed) J.A. Magallon
2002-06-12  0:00     ` Andrea Arcangeli
2002-06-10 18:50   ` Mike Kravetz
2002-06-10 20:02     ` Ingo Molnar
2002-06-12 11:54       ` David S. Miller
2002-06-12 16:57         ` [patch] switch_mm()'s desire to run without the rq lock Ingo Molnar
2002-06-12 21:54           ` David S. Miller
2002-06-12 22:31           ` David S. Miller

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=1023755255.21155.166.camel@sinai \
    --to=rml@tech9.net \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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