All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: Xu CanHao <xucanhao@gmail.com>
Cc: Zan Lynx <zlynx@acm.org>, reiserfs-devel@vger.kernel.org
Subject: Re: Question about memory pressure freezes
Date: Sun, 29 Jul 2007 01:36:49 +0400	[thread overview]
Message-ID: <46ABB6F1.6060304@namesys.com> (raw)
In-Reply-To: <6ec7a4340707271852y870e692sd7dddbe2916e4779@mail.gmail.com>

Xu CanHao wrote:

>Hello!
>
>    Since the default atom_max_size is RAM/4, that means 256MB of
>maximum atom in your computer, and your HDD does 30MB/s which means
>you'll have 8s-9s "flush/system freeze" time.
>
>    IIRC, edward said the atom_max_size mount option is useless,
>

It is  useless for remount, in other cases it works fine
(for root file system it makes sense to edit fstab).
So you can pass the option "tmgr.atom_max_size=N",
where N  is atom size in blocks

> so
>I'd suggest you modify your reiser4/init_super.c and change:
>       sbinfo->tmgr.atom_max_size = totalram_pages / 4;
>to
>       sbinfo->tmgr.atom_max_size = totalram_pages / 16;
>which means your atom would have a maximum size of 64MB and a maximum
>freeze time of only 2 seconds.
>  
>

Such nice linear dependency disappears with some workload,
so freeze time is not comforting also for small atoms..

>Thanks!
>
>
>2007/7/28, Zan Lynx <zlynx@acm.org>:
>  
>
>>Edward answered my question mostly.
>>
>>But, I have 1 GB RAM and a Hitachi 7,200 RPM laptop drive.  It does
>>about 30 MB/s.
>>
>>On Fri, 2007-07-27 at 09:40 +0800, Xu CanHao wrote:
>>    
>>
>>>Hello!
>>>
>>>   How much is your RAM?
>>>   What is the result of your HDD's hdparm -t?
>>>
>>>Thanks!
>>>
>>>2007/7/27, Zan Lynx <zlynx@acm.org>:
>>>      
>>>
>>>>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>
>>>>
>>>>
>>>>        
>>>>
>>--
>>Zan Lynx <zlynx@acm.org>
>>
>>
>>    
>>
>-
>To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>  
>


  reply	other threads:[~2007-07-28 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 22:25 Question about memory pressure freezes Zan Lynx
2007-07-27 14:54 ` 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 [this message]
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=46ABB6F1.6060304@namesys.com \
    --to=edward@namesys.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=xucanhao@gmail.com \
    --cc=zlynx@acm.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.