From: "Matthew Kirk" <mkirk01@rcn.com>
To: "'Andrew Morton'" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: fsync occasionally very slow
Date: Fri, 26 Jan 2007 14:33:36 -0500 [thread overview]
Message-ID: <000c01c74180$dfe71070$6600a8c0@charm> (raw)
In-Reply-To: <20070126031654.a41fe374.akpm@osdl.org>
Sorry, this will show my ignorance... my system is lacking
/proc/sysrq-trigger. I can find how to build a kernel with the magic sysrq
key (CONFIG_MAGIC_SYSRQ=y), and have done so, but I still don't have
/proc/sysrq-* and cannot seem to find how to build in sysrq functionality
itself - assuming that's what's missing. Presumably it's something in
.config I'm just not seeing?
Thanks again!
Matt
-----Original Message-----
From: Andrew Morton [mailto:akpm@osdl.org]
Sent: Friday, January 26, 2007 6:17 AM
To: Matthew Kirk
Cc: linux-kernel@vger.kernel.org
Subject: Re: fsync occasionally very slow
On Fri, 26 Jan 2007 05:37:38 -0500
"Matthew Kirk" <mkirk01@rcn.com> wrote:
> I am working on an application that fsync(2) files and directories as
> needed. I’m seeing intermittent stalls on fsync that can last many
> seconds.
Please generate an all-task backtrace during the stall via:
dmesg -n 8
<wait for a stall>
echo t > /prov/sysrq-trigger
dmesg -s 1000000 > foo
and send foo.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.11/652 - Release Date: 1/25/2007
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.12/653 - Release Date: 1/26/2007
next prev parent reply other threads:[~2007-01-26 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 10:37 fsync occasionally very slow Matthew Kirk
2007-01-26 11:16 ` Andrew Morton
2007-01-26 19:33 ` Matthew Kirk [this message]
2007-01-26 19:48 ` Andrew Morton
2007-01-31 13:18 ` Matthew Kirk
2007-01-29 22:02 ` Matthew Kirk
2007-01-29 23:22 ` Andrew Morton
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='000c01c74180$dfe71070$6600a8c0@charm' \
--to=mkirk01@rcn.com \
--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