From: Timothy Miller <miller@techsource.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Andrew Morton <akpm@osdl.org>, Grant Miner <mine0057@mrs.umn.edu>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: Filesystem Tests
Date: Wed, 06 Aug 2003 19:37:42 -0400 [thread overview]
Message-ID: <3F319146.6080607@techsource.com> (raw)
In-Reply-To: 3F310B6D.6010608@namesys.com
Hans Reiser wrote:
> reiser4 cpu consumption is still dropping rapidly as others and I find
> kruft in the code and remove it. Major kruft remains still.
If a file system is getting greater throughput, that means the relevant
code is being run more, which means more CPU will be used for the
purpose of setting up DMA, etc. That is, if a FS gets twice the
throughput, it would not be unreasonable to expect it to use 2x the CPU
time.
Furthermore, in order to achieve greater throughput, one has to write
more intelligent code. More intelligent code is probably going to
require more computation time.
That is to say, if your FS is twice as fast, saying it has a problem
purely on the basis that it's using more CPU ignores certain facts and
basic logic.
Now, if you can manage to make it twice as fast while NOT increasing the
CPU usage, well, then that's brilliant, but the fact that ReiserFS uses
more CPU doesn't bother me in the least.
next prev parent reply other threads:[~2003-08-06 23:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 2:30 Filesystem Tests Grant Miner
2003-08-06 3:47 ` Peter Chubb
2003-08-06 10:43 ` Oleg Drokin
2003-08-06 5:41 ` Andrew Morton
2003-08-06 10:35 ` Szakacsits Szabolcs
2003-08-09 1:09 ` Jamie Lokier
2003-08-09 5:12 ` Szakacsits Szabolcs
2003-08-09 9:33 ` Jamie Lokier
2003-08-09 9:18 ` Szakacsits Szabolcs
2003-08-09 16:19 ` Jamie Lokier
2003-08-10 21:03 ` Grant Miner
2003-08-12 8:27 ` Dieter Nützel
2003-08-06 14:06 ` Hans Reiser
2003-08-06 16:34 ` Diego Calleja García
2003-08-06 18:04 ` Mike Fedyk
2003-08-06 18:45 ` Diego Calleja García
2003-08-06 19:08 ` Mike Fedyk
2003-08-06 19:40 ` Diego Calleja García
2003-08-07 13:51 ` Hans Reiser
2003-08-07 0:55 ` Clemens Schwaighofer
2003-08-06 21:19 ` Andrew Morton
2003-08-06 21:25 ` ieee1394 (Firewire) driver problem Henrik Raeder Clausen
2003-08-07 12:55 ` Filesystem Tests Hans Reiser
2003-08-07 19:09 ` Diego Calleja García
2003-08-07 19:21 ` ahorn
2003-08-06 23:37 ` Timothy Miller [this message]
2003-08-06 23:47 ` Mike Fedyk
2003-08-07 0:40 ` Timothy Miller
2003-08-07 13:55 ` jlnance
2003-08-06 9:55 ` Felipe Alfaro Solana
2003-08-06 10:48 ` Paul Dickson
2003-08-06 11:39 ` Grant Miner
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=3F319146.6080607@techsource.com \
--to=miller@techsource.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mine0057@mrs.umn.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox