From: Paulo Marques <pmarques@grupopie.com>
To: Thomas Charbonnel <thomas@undata.org>
Cc: Ingo Molnar <mingo@redhat.com>, Shane Shrybman <shrybman@aei.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] voluntary-preempt-2.6.8-rc2-O2
Date: Fri, 06 Aug 2004 19:44:47 +0100 [thread overview]
Message-ID: <4113D19F.8060608@grupopie.com> (raw)
In-Reply-To: <1091815684.7586.28.camel@localhost>
Thomas Charbonnel wrote:
>....
> While accessing the file system (this one is very frequent):
>
> Aug 2 15:32:24 satellite (bash/5298): 1095us non-preemptible critical
> section violated 1000 us preempt threshold starting at
> search_by_key+0x120/0x1140 and ending at voluntary_resched+0x1a/0x70
> Aug 2 15:32:24 satellite [<c010574e>] dump_stack+0x1e/0x30
> Aug 2 15:32:24 satellite [<c01171a6>] touch_preempt_timing+0x36/0x50
> Aug 2 15:32:24 satellite [<c042856a>] voluntary_resched+0x1a/0x70
> Aug 2 15:32:24 satellite [<c0158c44>] __getblk+0x44/0x70
> Aug 2 15:32:24 satellite [<c01ae348>] search_by_key+0x78/0x1140
> Aug 2 15:32:24 satellite [<c01af4bc>]
> search_for_position_by_key+0xac/0x3f0
> Aug 2 15:32:24 satellite [<c019e0c4>]
> reiserfs_allocate_blocks_for_region+0x354/0x15b0
> Aug 2 15:32:24 satellite [<c01a0c4c>] reiserfs_file_write+0x61c/0x8d0
^^^^^^^^
I remember some discussion on a "voluntary preempt" thread, about
reiserfs being bad for latency.
You might search the archives for this, but as far as I remember, ext3
was a better alternative, latency-wise.
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-08-06 18:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 15:08 Shane Shrybman
2004-08-03 9:19 ` Ingo Molnar
2004-08-03 14:05 ` Shane Shrybman
2004-08-03 14:09 ` Ingo Molnar
2004-08-03 14:45 ` Shane Shrybman
2004-08-03 16:29 ` Ingo Molnar
2004-08-03 17:43 ` Shane Shrybman
2004-08-03 14:19 ` Ingo Molnar
2004-08-04 11:22 ` Rudo Thomas
2004-08-04 11:54 ` Ingo Molnar
2004-08-04 16:05 ` Rudo Thomas
2004-08-04 14:32 ` Peter Zijlstra
2004-08-04 14:34 ` [patch] voluntary-preempt-2.6.8-rc2-mm2-O3 Peter Zijlstra
2004-08-06 18:08 ` [patch] voluntary-preempt-2.6.8-rc2-O2 Thomas Charbonnel
2004-08-06 18:44 ` Paulo Marques [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 18:46 David M
2004-07-13 14:39 preempt-timing-2.6.8-rc1 William Lee Irwin III
2004-07-25 5:15 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-25 22:49 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-26 8:23 ` preempt-timing-2.6.8-rc1 Ingo Molnar
2004-07-26 8:29 ` preempt-timing-2.6.8-rc1 Lee Revell
2004-07-26 8:35 ` [patch] voluntary-preempt-2.6.8-rc2-J3 Ingo Molnar
2004-07-26 9:00 ` Lee Revell
2004-07-26 12:40 ` Ingo Molnar
2004-07-26 20:47 ` [patch] voluntary-preempt-2.6.8-rc2-J7 Ingo Molnar
2004-07-29 22:26 ` [patch] voluntary-preempt-2.6.8-rc2-M5 Ingo Molnar
2004-08-01 19:30 ` [patch] voluntary-preempt-2.6.8-rc2-O2 Ingo Molnar
2004-08-01 22:40 ` Felipe Alfaro Solana
2004-08-01 23:20 ` Daniel Schmitt
2004-08-02 6:21 ` Felipe Alfaro Solana
2004-08-01 23:44 ` Matt Heler
2004-08-02 6:26 ` Felipe Alfaro Solana
2004-08-02 7:47 ` Ingo Molnar
2004-08-02 1:45 ` Lee Revell
2004-08-02 2:14 ` Lee Revell
2004-08-02 7:56 ` Ingo Molnar
2004-08-02 13:42 ` Lenar Lõhmus
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=4113D19F.8060608@grupopie.com \
--to=pmarques@grupopie.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shrybman@aei.ca \
--cc=thomas@undata.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
Powered by JetHome