From: Alexander Gran <alex@zodiac.dnsalias.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1-mm3
Date: Thu, 26 Jan 2006 02:48:01 +0100 [thread overview]
Message-ID: <200601260248.01357@zodiac.zodiac.dnsalias.org> (raw)
In-Reply-To: <20060125092117.03c69174.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Am Mittwoch, 25. Januar 2006 18:21 schrieb Andrew Morton:
> Strange. It might be worth checking 2.6.16-rc1-git4.
Hmm. I need reiser4. I'll have to see how I get that into git-4. ok
> If the CPU load is high (ie: 100%) during the delay, and it's mostly system
> time then yes, a kernel profile would be interesting.
> Documentation/basic_profiling.txt has details.
No, Cpu is at 600Mhz (Centrino, would increase to 1600 if load demands), and
running at ~10%.
The delays must have an other reason. It makes no difference at all if i hit
skip-over on something like
i *= 1;
or
doSomePrettyHeavyThing();
which imo prooves that there is no cpu-performance bottleneck.
regards
Alex
--
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-26 1:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 13:48 2.6.16-rc1-mm3 Alexander Gran
2006-01-25 17:21 ` 2.6.16-rc1-mm3 Andrew Morton
2006-01-26 1:48 ` Alexander Gran [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-25 7:24 2.6.16-rc1-mm3 Andrew Morton
2006-01-25 10:44 ` 2.6.16-rc1-mm3 Reuben Farrelly
2006-01-26 5:39 ` [linux-usb-devel] 2.6.16-rc1-mm3 Greg KH
2006-01-27 12:46 ` Reuben Farrelly
2006-01-27 17:27 ` Greg KH
2006-01-27 17:49 ` 2.6.16-rc1-mm3 Pete Zaitcev
2006-01-27 19:40 ` 2.6.16-rc1-mm3 Reuben Farrelly
2006-01-27 19:57 ` 2.6.16-rc1-mm3 Pete Zaitcev
2006-01-25 11:40 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-25 15:59 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-26 19:02 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-26 19:47 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-26 19:50 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-27 10:11 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-01 8:30 ` 2.6.16-rc1-mm3 Nick Piggin
2006-02-01 8:51 ` 2.6.16-rc1-mm3 Andrew Morton
2006-02-02 21:06 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-02 22:20 ` 2.6.16-rc1-mm3 Andrew Morton
2006-02-02 23:48 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-03 0:12 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-26 19:58 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-25 14:06 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-25 14:44 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-25 16:46 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-25 18:16 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-25 21:06 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-26 7:03 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-27 0:20 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-27 3:23 ` 2.6.16-rc1-mm3 Andrew Morton
2006-01-27 6:03 ` 2.6.16-rc1-mm3 Eric Dumazet
2006-01-27 10:12 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-27 10:37 ` 2.6.16-rc1-mm3 Eric Dumazet
2006-01-27 11:47 ` 2.6.16-rc1-mm3 Reuben Farrelly
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=200601260248.01357@zodiac.zodiac.dnsalias.org \
--to=alex@zodiac.dnsalias.org \
--cc=akpm@osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).