From: Gabriel Devenyi <devenyga@mcmaster.ca>
To: ck@vds.kolivas.org
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: [ck] Re: Preempt Threshold Measurements
Date: Mon, 12 Jul 2004 23:09:43 -0400 [thread overview]
Message-ID: <200407122309.43088.devenyga@mcmaster.ca> (raw)
In-Reply-To: <20040713025502.GR21066@holomorphy.com>
Ah good, thanks for the suggestion on how to improve this... Now, what exactly
is that, and where/how do I change it.... (I really should start/finish that
"understanding the linux kernel" book of mine)
--
Gabriel Devenyi
devenyga@mcmaster.ca
On Monday 12 July 2004 22:55, William Lee Irwin III wrote:
> On Mon, Jul 12, 2004 at 10:48:50PM -0400, Gabriel Devenyi wrote:
> > Well I'm not particularly educated in kernel internals yet, here's some
> > reports from the system when its running.
> > 6ms non-preemptible critical section violated 4 ms preempt threshold
> > starting at do_munmap+0xd2/0x140 and ending at do_munmap+0xeb/0x140
> > [<c014007b>] do_munmap+0xeb/0x140
> > [<c01163b0>] dec_preempt_count+0x110/0x120
> > [<c014007b>] do_munmap+0xeb/0x140
> > [<c014010f>] sys_munmap+0x3f/0x60
> > [<c0103ee1>] sysenter_past_esp+0x52/0x71
>
> Looks like ZAP_BLOCK_SIZE may be too large for you. Lowering that some
> may "help" this. It's probably harmless, but try lowering that to half
> of whatever it is now, or maybe 64*PAGE_SIZE. It may be worthwhile
> to restructure how the preemption points are done in unmap_vmas() so
> we don't end up in some kind of tuning nightmare.
>
>
> -- wli
> _______________________________________________
> ck@vds.kolivas.org
> ck mailing list - unmoderated. Please reply-to-all when posting.
> http://bhhdoa.org.au/mailman/listinfo/ck
next prev parent reply other threads:[~2004-07-13 3:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:43 Preempt Threshold Measurements Gabriel Devenyi
2004-07-12 23:59 ` Con Kolivas
2004-07-13 0:15 ` Gabriel Devenyi
2004-07-13 2:40 ` William Lee Irwin III
2004-07-13 2:48 ` [ck] " Gabriel Devenyi
2004-07-13 2:54 ` Con Kolivas
2004-07-13 4:01 ` Andrew Morton
2004-07-13 5:51 ` Con Kolivas
2004-07-13 6:14 ` Andrew Morton
2004-07-13 8:03 ` Lee Revell
2004-07-13 10:26 ` Con Kolivas
2004-07-13 21:52 ` Con Kolivas
2004-07-13 10:08 ` William Lee Irwin III
2004-07-13 10:40 ` William Lee Irwin III
2004-07-13 11:07 ` Lenar Lõhmus
2004-07-13 11:13 ` William Lee Irwin III
2004-07-13 2:55 ` [ck] " William Lee Irwin III
2004-07-13 3:09 ` Gabriel Devenyi [this message]
2004-07-13 4:07 ` Andrew Morton
2004-07-13 5:34 ` Con Kolivas
2004-07-13 5:48 ` Nick Piggin
2004-07-13 10:14 ` William Lee Irwin III
2004-07-14 10:15 ` [ck] " Jens Bergmann
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=200407122309.43088.devenyga@mcmaster.ca \
--to=devenyga@mcmaster.ca \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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