Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Pavel Kiryukhin <vksavl@gmail.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH][MIPS] fix user_cpus_allowed assignment
Date: Fri, 21 Dec 2007 02:11:22 +0100	[thread overview]
Message-ID: <20071221011122.GB14926@linux-mips.org> (raw)
In-Reply-To: <017c01c840cb$7a5049c0$10eca8c0@grendel>

On Mon, Dec 17, 2007 at 05:40:03PM +0100, Kevin D. Kissell wrote:

> This looks to be a correct fix.  Long term, we really do need to convince
> the scheduler maintainer to provide hooks that will allow hardware-driven
> affinity to be integrated with application-driven affinity in a sensible way,
> without requiring replication (and replicated maintenence) of the system
> call code in private copies like this.  I asked for such hooks in sched.c
> when it first became apparent that dynamic FPU affinity was desirable,
> but was blown off at that time, so, with regret, I perpetrated the local copy
> hack.  But it's silly, and MIPS can't possibly be the only architecture where 
> Linux is used in systems with assymmetric resources where adaptive affinity 
> is useful.

I dare to speculate that the new job of a certain Mike Uhler may increase
the need for such a scheduler feature :-)

  Ralf

      parent reply	other threads:[~2007-12-21  1:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 13:17 [PATCH][MIPS] fix user_cpus_allowed assignment Pavel Kiryukhin
2007-12-17 16:40 ` Kevin D. Kissell
2007-12-17 16:40   ` Kevin D. Kissell
2007-12-21  1:11   ` Ralf Baechle [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=20071221011122.GB14926@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=vksavl@gmail.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