All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: zam, please discuss this
Date: Wed, 23 Jun 2004 21:29:48 -0700	[thread overview]
Message-ID: <40DA58BC.1060203@namesys.com> (raw)
In-Reply-To: <20040623063049.GA5080@backtop.namesys.com>

Alex Zarochentsev wrote:

>On Tue, Jun 22, 2004 at 07:29:33PM -0700, Hans Reiser wrote:
>  
>
>>http://www.namesys.com/intbenchmarks/mongo/04.05.04/256MB.RAM/comparison/smart-8k.noENTD.vs.ENTD/comp-ENTD.vs.noENTD.html
>>    
>>
>
>Because direct page reclaiming (when a thread which needs memory does 
>try_to_relase_page() by itself) is better then indirect one (through
>ENTD or whatever page reclaiming daemon).  It is why Linux uses direct
>page reclaiming not indirect.
>
>  
>
I apologize to zam, I meant to only cc this to reiserfs-dev. 

 I think this performance loss can be overcome, and needs to be overcome 
so we can eliminate emergency flush and get good iozone results.  I 
should note though that Andrew Morton thinks iozone is a benchmark that 
does things that no application does (dirtying massive amounts of mmap'd 
pages).  I am curious as to whether the sysadmins on the list would 
agree with that (Andrew may be right)....

  parent reply	other threads:[~2004-06-24  4:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  2:29 zam, please discuss this Hans Reiser
2004-06-23  6:30 ` Alex Zarochentsev
2004-06-24  3:33   ` Hans Reiser
2004-06-24  4:29   ` Hans Reiser [this message]
2004-06-23 18:03     ` iozone reality check: was " George Beshers
2004-06-24  5:13       ` Hans Reiser
2004-06-23 18:36         ` George Beshers
2004-06-24  7:11           ` Hans Reiser

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=40DA58BC.1060203@namesys.com \
    --to=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.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 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.