From: Hans Reiser <reiser@namesys.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Steve French <smfrench@austin.rr.com>,
cliff white <cliffw@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: cifs large write performance improvements to Samba
Date: Thu, 16 Dec 2004 10:58:07 -0800 [thread overview]
Message-ID: <41C1DABF.2050004@namesys.com> (raw)
In-Reply-To: <20041216121151.GH8246@logos.cnet>
Marcelo Tosatti wrote:
>
>> I have not seen anyone
>>doing that on Linux in an automated fashion (e.g running iozone
>>automated every time a new 2.6.x.rc on a half a dozen of the fs - simply
>>to verify that things had not gotten drastically worse on a particular
>>fs due to a bug or sideffect of a global VFS change).
>>
>>
>
>Yes, we definately need that.
>
>
>
Andrew Morton is saying that iozone does things real apps don't do, that
is, it dirties mmap'd pages enough to swamp the machine.
Do you guys agree or disagree with that?
Reiser4 needs iozone optimization work which we haven't bothered with yet.
next prev parent reply other threads:[~2004-12-16 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 16:56 cifs large write performance improvements to Samba Steve French
2004-12-13 17:20 ` cliff white
2004-12-13 18:34 ` Steve French
2004-12-13 18:43 ` Steve French
2004-12-16 12:11 ` Marcelo Tosatti
2004-12-16 16:39 ` automated filesystem testing for multiple Linux fs Steve French
2004-12-17 0:27 ` Michael Clark
2004-12-17 0:51 ` Steve French
2004-12-17 2:23 ` Michael Clark
2004-12-16 18:58 ` Hans Reiser [this message]
2004-12-16 16:30 ` cifs large write performance improvements to Samba Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 5:45 Steve French
2004-12-13 14:38 ` bert hubert
[not found] ` <41BDC911.9010600@austin.rr.com>
2004-12-22 14:56 ` bert hubert
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=41C1DABF.2050004@namesys.com \
--to=reiser@namesys.com \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=smfrench@austin.rr.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