From: Zan Lynx <zlynx@acm.org>
To: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Question about memory pressure freezes
Date: Thu, 26 Jul 2007 16:25:57 -0600 [thread overview]
Message-ID: <1185488757.33588.6.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
I have often experienced nearly full system freezes for up to five
seconds at a time while memory is being flushed to disk.
I'm not sure if this is a general Linux problem or a Reiser4 problem, so
I thought I'd ask.
A sysrq-T during the freeze shows many processes trying to acquire a
memory page, and Reiser4 flushing atoms and doing sync things.
My working theory right now is that Reiser4 spends time flushing a lot
of data at once before returning.
If I am right about that, would it not make more sense to flush a few
pages, return to the kernel, flush a few more pages, return to the
kernel, etc, etc? That way programs could get a bit of RAM and make
some progress.
Of course I could be completely off about what's going on.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-07-26 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 22:25 Zan Lynx [this message]
2007-07-27 14:54 ` Question about memory pressure freezes Edward Shishkin
[not found] ` <6ec7a4340707261840r34a68951s26a2691778c3ca15@mail.gmail.com>
[not found] ` <1185557881.8434.6.camel@localhost>
2007-07-28 1:52 ` Xu CanHao
2007-07-28 21:36 ` Edward Shishkin
2007-07-29 3:11 ` Xu CanHao
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=1185488757.33588.6.camel@localhost \
--to=zlynx@acm.org \
--cc=reiserfs-devel@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 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.