From: Erich Focht <efocht@ess.nec.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: O(1) scheduler "complex" macros
Date: Thu, 11 Jul 2002 09:25:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905763@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905752@msgid-missing>
Ingo,
the last fix survived one night of testing with included udelay(100), so
I would consider it stable. Thanks again!
The performance with the new "complex" macros is as expected worse than
with the simple ones, we see 10% in some cases, which is hurting a lot.
Would you please consider moving the location of the switch_lock from
the end of the task_struct to the hot area near the scheduler related
variables? The effect may vary depending on the cache line size but
having it behind *array or sleep_timestamp would probably save us a cache
miss here.
Regards,
Erich
next prev parent reply other threads:[~2002-07-11 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 9:05 [Linux-ia64] Re: O(1) scheduler "complex" macros Erich Focht
2002-07-10 12:34 ` Erich Focht
2002-07-10 18:31 ` Ingo Molnar
2002-07-10 19:30 ` Ingo Molnar
2002-07-11 9:25 ` Erich Focht [this message]
2002-07-11 9:31 ` Ingo Molnar
2002-07-11 9:39 ` Ingo Molnar
2002-07-11 9:52 ` Ingo Molnar
2002-07-12 12:39 ` Pavel Machek
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=marc-linux-ia64-105590701905763@msgid-missing \
--to=efocht@ess.nec.de \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.