From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Question on IICACHE and mount info (2.4.19-pre5)
Date: Mon, 08 Apr 2002 14:45:58 +0200 [thread overview]
Message-ID: <3CB19106.90401@mb.tu-ilmenau.de> (raw)
In-Reply-To: 20020408160226.A937@namesys.com
On 04/08/2002 02:02 PM, Oleg Drokin wrote:
> Hello!
>
> On Mon, Apr 08, 2002 at 01:44:48PM +0200, Manuel Krause wrote:
>
>
[...]
> Noborder is evil right now, don't use it if you are not sure what are you
> doing ;)
O.k., _then_ I should not use it! :-))
[...]
> Hm, things are not so good here.
>
> Too bad you do not have any file-size distribution statistics.
Is there an easy way to get this info from the filesystems?
>>Yes, I have differences. But I think they're not the ones we wanted to
>>see?! I double checked the lines I pasted to this email ;-)
>>
>
> I believe right now we have better patches to speed-up things both on read
> (IDE only) and write that we are testing mostly locally.
Could you make them available on the namesys server? ;-)
> iicache only speedups some reads on large files (I have not looked at
> new iicache write support yet, so my observations are only can be applied
> up to iicache-9 patch)
>
> Bye,
> Oleg
Thanks,
Manuel
next prev parent reply other threads:[~2002-04-08 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 0:00 Question on IICACHE and mount info (2.4.19-pre5) Manuel Krause
2002-04-05 5:02 ` Oleg Drokin
2002-04-05 13:27 ` Manuel Krause
2002-04-05 13:37 ` Oleg Drokin
2002-04-08 11:44 ` Manuel Krause
2002-04-08 12:02 ` Oleg Drokin
2002-04-08 12:45 ` Manuel Krause [this message]
2002-04-08 12:57 ` Nikita Danilov
2002-04-08 12:59 ` Oleg Drokin
2002-04-08 15:02 ` Hans Reiser
2002-04-05 12:50 ` Yury Yu. Rupasov
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=3CB19106.90401@mb.tu-ilmenau.de \
--to=manuel.krause@mb.tu-ilmenau.de \
--cc=green@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.