linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Erley <paterley@mail.drunkencodepoets.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] trivial change in kernel/sched.c in 2.6.0-test9+
Date: Thu, 27 Nov 2003 11:46:31 -0500	[thread overview]
Message-ID: <20031127114631.06f71eb7.paterley@mail.drunkencodepoets.com> (raw)
In-Reply-To: <20031126110250.GB27967@actcom.co.il>

> > If you can suggest a way to test this, I will test it on my system 
> > tomorrow.
> 
> Just off the top of my head, you could try something like a kernel
> compilation with and without it. I doubt you'll see any improvement,
> though.. there are very few places in the kernel where such
> micro-optimizations are worth it, IMVHO. 


Well, I ran about 6 different compiles each on a patched and an unpatched,
and my 'average' savings were about 1 second per 6 minute compile, which is
negligible.  I wonder if doing a make is a good test of this.  Can anyone else
out there come up with another way to check this with a non-cpu hog
application?  I'd like some other cases to test this in.  I mean, when you do 
a 'large' number of compiles that each take a half second, I can see
that saving a division and an addition really wouldn't make a big difference,
but in a situation where you have a large number of short lived threads in
a child process, it may end up saving a bit more.

Pat Erley

      reply	other threads:[~2003-11-27 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  5:27 [patch] trivial change in kernel/sched.c in 2.6.0-test9+ Pat Erley
2003-11-26  5:55 ` Muli Ben-Yehuda
2003-11-26  6:07   ` s0be
2003-11-26 11:02     ` Muli Ben-Yehuda
2003-11-27 16:46       ` Pat Erley [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=20031127114631.06f71eb7.paterley@mail.drunkencodepoets.com \
    --to=paterley@mail.drunkencodepoets.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    /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).