linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: UP optimizations ..
Date: Wed, 27 Aug 2003 20:34:28 +0200	[thread overview]
Message-ID: <20030827183428.GA18614@www.13thfloor.at> (raw)
In-Reply-To: <16204.62914.298711.293389@gargle.gargle.HOWL>

On Wed, Aug 27, 2003 at 08:17:38PM +0200, Mikael Pettersson wrote:
> Herbert =?iso-8859-1?Q?P=F6tzl?= writes:
>  > 
>  > Hi Mikael!
>  > Hi Marcelo!
>  > 
>  > stumbled repeatedly over the patches (or what remained of them)
>  > from Mikael?, replacing task->processor and friends by inline
>  > functions task_cpu(task), to eliminate them on UP systems ...
>  > 
>  > my questions: 
>  >  - is there an up to date patchset?
> 
> Yes, I've kept it up to date. In fact I've been using it in
> every single 2.4 kernel I've built for the last 18+ months.
> Lately also on ppc32 and x86-64.
> 
> Below is the current UP micro-optimisation patch set for 2.4.22.
> It changes p->processor, p->cpus_allowed, and p->cpus_runnable
> accesses (reads and writes) to use inline functions. In UP kernels
> these reduce to doing nothing or returning a constant.
> 
> To keep the patch small, it doesn't change accesses in SMP-only code.
> (This is also the reason why p->cpus_runnable only has a wrapper for
> updates, since all reads are in SMP-only code.)

good to know ... will use it in my patchset (now with reference ;)
let me know if you add/fix something ...

thanks for the patch,
Herbert

> /Mikael

  reply	other threads:[~2003-08-27 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 16:03 UP optimizations Herbert Pötzl
2003-08-27 18:17 ` Mikael Pettersson
2003-08-27 18:34   ` Herbert Pötzl [this message]
2003-08-28  8:23   ` Daniel Egger
2003-08-29  6:53     ` Jamie Lokier

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=20030827183428.GA18614@www.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mikpe@csd.uu.se \
    /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 NNTP newsgroup(s).