All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Schäfer" <gentryx@gmx.de>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: State of the Reiser4 FS
Date: Wed, 15 Mar 2006 09:57:45 +0100	[thread overview]
Message-ID: <20060315085745.GA21609@wintermute> (raw)
In-Reply-To: <4417BEC4.6060506@namesys.com>

On 23:14 Tue 14 Mar     , Hans Reiser wrote:
> I generally believe that the per 4k
> approach used throughout the linux kernel is not as CPU efficient as
> sending larger groups of pages through the layers all at once.  In other
> words, there is a reason we have bios, and we need to learn the lesson
> from them that they teach us, and abstract it into a general design
> approach.

This is a bit OT, but still: I think you're absolutely right there. This 4k 
approach causes funny thing even in completely different areas. 

I've recently been playing around with openMosix (transparent process 
migration between Linux hosts over the network) and there the write 
preformance is totally spoiled (>50% performance loss) just because 
copy_from_user is only called for 4k block when writing (and these 
requests then suffer from the high network latency). 

If larger blocks would be used, this performance flaw wouldn't exist at 
all... Just my 2 cents

-Andreas

  reply	other threads:[~2006-03-15  8:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 10:41 State of the Reiser4 FS Avuton Olrich
2006-03-14 11:45 ` Vladimir V. Saveliev
2006-03-14 15:32   ` Clemens Eisserer
2006-03-15  7:14     ` Hans Reiser
2006-03-15  8:57       ` Andreas Schäfer [this message]
2006-03-15 18:29         ` Hans Reiser
2006-03-15 19:27           ` Andreas Schäfer
2006-03-15 21:08             ` Andreas Dilger
2006-03-16  0:58             ` 4k at a time only works well for an OS that does less per iteration than Linux does Hans Reiser
2006-03-15 19:45       ` State of the Reiser4 FS Jonathan Briggs
2006-03-15 20:43         ` Hans Reiser
2006-03-15 21:25           ` Andreas Schäfer
2006-03-15  8:45 ` Hans Reiser
2006-03-15 12:59   ` Avuton Olrich
2006-03-15 18:33     ` Hans Reiser
2006-03-26 11:27       ` 2.6.16 patch jp
2006-03-27 17:27         ` jp
2006-03-28 11:42           ` Vladimir V. Saveliev
2006-03-28 12:54             ` Tassilo Horn
2006-03-28 17:12               ` Danny Milosavljevic
2006-03-28 18:00                 ` Tassilo Horn
2006-03-28 23:22             ` Jake Maciejewski
2006-03-27 20:10         ` Marcus Furlong
2006-03-27 19:44           ` Tassilo Horn
2006-03-27 21:32             ` Marcus Furlong
2006-03-27 20:41               ` Tassilo Horn
2006-03-27 21:29               ` Tassilo Horn

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=20060315085745.GA21609@wintermute \
    --to=gentryx@gmx.de \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@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.