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 22:48:50 -0400 [thread overview]
Message-ID: <200407122248.50377.devenyga@mcmaster.ca> (raw)
In-Reply-To: <20040713024051.GQ21066@holomorphy.com>
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
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
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
5ms 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
--
Gabriel Devenyi
devenyga@mcmaster.ca
On Monday 12 July 2004 22:40, William Lee Irwin III wrote:
> On Mon, Jul 12, 2004 at 07:43:25PM -0400, Gabriel Devenyi wrote:
> > Keeping in mind that I'm using the nvidia-kernel drivers, here are my
> > preempt threshold violations.
> > 6ms non-preemptible critical section violated 4 ms preempt threshold
> > starting at kernel_fpu_begin+0xd/0x50 and ending at
> > _mmx_memcpy+0x127/0x170 [<c0241987>] _mmx_memcpy+0x127/0x170
> > [<c01163b0>] dec_preempt_count+0x110/0x120
> > [<c0241987>] _mmx_memcpy+0x127/0x170
> > [<c012d3b5>] load_module+0x835/0x900
> > [<c013c84e>] unmap_vmas+0x10e/0x1f0
> > [<c012d4fb>] sys_init_module+0x7b/0x230
> > [<c0103ee1>] sysenter_past_esp+0x52/0x71
>
> Things tend to be slow and stupid in the interest of robustness during
> system initialization.
>
> I'd suggest ignoring those unless you're specifically interested in boot
> time (in which case you should be doing things for yourself) and focusing
> on ones reported during normal usage after the system is up.
>
>
> -- 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 2:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:43 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 ` Gabriel Devenyi [this message]
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
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=200407122248.50377.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
all inboxes | Powered by JetHome®