From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Antti Lankila <alankila@elma.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: elevator=as related to my performance issues
Date: Mon, 19 Apr 2004 22:20:35 +1000 [thread overview]
Message-ID: <4083C413.90509@yahoo.com.au> (raw)
In-Reply-To: <Pine.A41.4.58.0404191355100.42820@tokka.elma.fi>
Antti Lankila wrote:
> I'm sorry that I can't post this mail in reply to the thread, this is
> because I'm not subscribed, so I can't reply.
>
[snip]
So it doesn't seem like you are losing interrupts. And
it doesn't appear to be confined to the anticpatory
scheduler - definitely nothing fundamental because setting
antic_expire = 0 still gives you problems.
The only other problems I can think of that you might be
having are chipset problems, or CPU scheduler problems.
Which reminds me, do you have your X server at nice 0?
If not, try:
renice 0 `pidof X`
and let us know how you go.
prev parent reply other threads:[~2004-04-19 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 11:54 elevator=as related to my performance issues Antti Lankila
2004-04-19 12:20 ` Nick Piggin [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=4083C413.90509@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alankila@elma.net \
--cc=linux-kernel@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