From: Andrea Arcangeli <andrea@suse.de>
To: linux-sound@vger.kernel.org
Subject: Re: [rtl] Low-latency patches working GREAT (<2.9ms audio latency),
Date: Mon, 06 Sep 1999 07:43:49 +0000 [thread overview]
Message-ID: <marc-linux-sound-93660371427710@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93588421815439@msgid-missing>
On Sat, 4 Sep 1999 yodaiken@fsmlabs.com wrote:
>on a uniprocessor. sct pointed out that reschedule_idle
>is very conservative about setting need_resched and this makes Ingo
>correct when he stated that need_resched>0 means that we really do need
>to resched. I'd be happier with some big database tests, and I really think
IMHO this is not the point at all.
need_resched = 1 means you _have_ to reschedule ASAP careless about the
scheduler algorithm at all.
>that database performance should be checked before any such change goes
>into the kernel, but for now, I was flat out wrong.
If honouring the need_resched bit is decreasing performances than it means
you _want_ to change the scheduler and not the code that honour the
need_resched bit. Of course I am supposing the checks itself are not the
source of the slowdown.
Andrea
prev parent reply other threads:[~1999-09-06 7:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-28 23:55 [rtl] Low-latency patches working GREAT (<2.9ms audio latency), see testresults ,but ISDN troubl yodaiken
1999-08-29 0:24 ` Alan Cox
1999-08-29 1:59 ` yodaiken
1999-08-29 6:21 ` [rtl] Low-latency patches working GREAT (<2.9ms audio latency), Linus Torvalds
1999-08-29 7:13 ` [rtl] Low-latency patches working GREAT (<2.9ms audio latency), see testresults ,but ISDN troubl Ingo Molnar
1999-08-29 7:15 ` Ingo Molnar
1999-08-29 7:17 ` Ingo Molnar
1999-08-29 13:59 ` yodaiken
1999-08-29 14:22 ` David Olofson
1999-08-29 20:48 ` yodaiken
1999-08-30 6:09 ` yodaiken
1999-08-30 6:55 ` Ingo Molnar
1999-08-30 7:30 ` Ingo Molnar
1999-08-30 8:18 ` yodaiken
1999-08-30 9:45 ` Ingo Molnar
1999-08-30 11:13 ` Stephen C. Tweedie
1999-09-04 20:41 ` yodaiken
1999-09-06 7:43 ` Andrea Arcangeli [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=marc-linux-sound-93660371427710@msgid-missing \
--to=andrea@suse.de \
--cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox