From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Jens Axboe <axboe@suse.de>, lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.46-mm2
Date: Sun, 10 Nov 2002 09:11:30 -0800 [thread overview]
Message-ID: <20021110171130.GJ23425@holomorphy.com> (raw)
In-Reply-To: <3DCE9034.6F833C31@digeo.com>
William Lee Irwin III wrote:
>> Go for it, I'm just trying to get tiobench to actually run (seems to
>> have new/different "die from too many threads" behavior wrt. --threads).
>> Dropping me a fresh kernel shouldn't slow anything down.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> It could be the procps thing? `tiobench --threads 256' shows up as a
> single process in top and ps due to the new thread consolidation feature.
> If you run `ps auxm' or hit 'H' in top, all is revealed. Not my fave
> feature that.
Turns out monitoring things via /proc/ slowed it down by some ridiculous
factor while it was trying to spawn threads. 9 hours became less than 1s
when I stopped looking.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> BLKELVGET/SET was removed
Okay, looks like there's an fs to use to get at it with.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
>> P.P.S: kgdb broke wchan reporting... investigating
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> ?
The wchan reporting needs to get taught about kern_schedule()
and user_schedule() so it can trim them off the stack, which
consists of moving them between scheduling_functions_start_here()
and scheduling_functions_end_here().
Bill
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Jens Axboe <axboe@suse.de>, lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.46-mm2
Date: Sun, 10 Nov 2002 09:11:30 -0800 [thread overview]
Message-ID: <20021110171130.GJ23425@holomorphy.com> (raw)
In-Reply-To: <3DCE9034.6F833C31@digeo.com>
William Lee Irwin III wrote:
>> Go for it, I'm just trying to get tiobench to actually run (seems to
>> have new/different "die from too many threads" behavior wrt. --threads).
>> Dropping me a fresh kernel shouldn't slow anything down.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> It could be the procps thing? `tiobench --threads 256' shows up as a
> single process in top and ps due to the new thread consolidation feature.
> If you run `ps auxm' or hit 'H' in top, all is revealed. Not my fave
> feature that.
Turns out monitoring things via /proc/ slowed it down by some ridiculous
factor while it was trying to spawn threads. 9 hours became less than 1s
when I stopped looking.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> BLKELVGET/SET was removed
Okay, looks like there's an fs to use to get at it with.
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
>> P.P.S: kgdb broke wchan reporting... investigating
On Sun, Nov 10, 2002 at 08:58:28AM -0800, Andrew Morton wrote:
> ?
The wchan reporting needs to get taught about kern_schedule()
and user_schedule() so it can trim them off the stack, which
consists of moving them between scheduling_functions_start_here()
and scheduling_functions_end_here().
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-11-10 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 3:59 2.5.46-mm2 Andrew Morton
2002-11-10 3:59 ` 2.5.46-mm2 Andrew Morton
2002-11-10 14:32 ` 2.5.46-mm2 Jens Axboe
2002-11-10 14:52 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 14:52 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 14:57 ` 2.5.46-mm2 Jens Axboe
2002-11-10 14:57 ` 2.5.46-mm2 Jens Axboe
2002-11-10 15:06 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 15:06 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 15:58 ` 2.5.46-mm2 Jens Axboe
2002-11-10 15:58 ` 2.5.46-mm2 Jens Axboe
2002-11-10 19:39 ` 2.5.46-mm2 Andrew Morton
2002-11-10 19:39 ` 2.5.46-mm2 Andrew Morton
2002-11-11 1:18 ` 2.5.46-mm2 William Lee Irwin III
2002-11-11 1:18 ` 2.5.46-mm2 William Lee Irwin III
2002-11-11 7:04 ` 2.5.46-mm2 Jens Axboe
2002-11-11 7:04 ` 2.5.46-mm2 Jens Axboe
2002-11-11 7:41 ` 2.5.46-mm2 William Lee Irwin III
2002-11-11 7:41 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 16:58 ` 2.5.46-mm2 Andrew Morton
2002-11-10 16:58 ` 2.5.46-mm2 Andrew Morton
2002-11-10 17:11 ` William Lee Irwin III [this message]
2002-11-10 17:11 ` 2.5.46-mm2 William Lee Irwin III
2002-11-10 23:10 ` 2.5.46-mm2 Toon van der Pas
2002-11-10 18:14 ` 2.5.46-mm2 - oops Ed Tomlinson
2002-11-10 18:14 ` Ed Tomlinson
2002-11-10 18:52 ` Andrew Morton
2002-11-10 18:52 ` Andrew Morton
2002-11-10 19:17 ` Ed Tomlinson
2002-11-10 19:17 ` Ed Tomlinson
2002-11-11 0:44 ` Denis Vlasenko
2002-11-11 0:44 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2002-11-11 4:37 2.5.46-mm2 Albert D. Cahalan
2002-11-11 7:43 ` 2.5.46-mm2 William Lee Irwin III
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=20021110171130.GJ23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.