From: Andrea Arcangeli <andrea@suse.de>
To: Momchil Velikov <velco@fadata.bg>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Radix tree page cache
Date: Thu, 31 Jan 2002 03:25:40 +0100 [thread overview]
Message-ID: <20020131032540.W1309@athlon.random> (raw)
In-Reply-To: <87sn8ny4af.fsf@fadata.bg>
In-Reply-To: <87sn8ny4af.fsf@fadata.bg>; from velco@fadata.bg on Wed, Jan 30, 2002 at 10:25:44PM +0200
On Wed, Jan 30, 2002 at 10:25:44PM +0200, Momchil Velikov wrote:
> Linus,
>
> Please, consider for inclusion in 2.5.3 series the following radix
> tree page cache patch.
Please benchmark on files 10giga large, only do cached I/O (reads are
fine) between 9G and 10G offset for example.
dbench or others handling not very huge files are not interesting
benchmarks for this, for them per-inode rbtree was faster too. the only
problem are the very huge files, the hashtable guarantees the same
performance on small and huge files.
Andrea
next prev parent reply other threads:[~2002-01-31 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 20:25 [PATCH] Radix tree page cache Momchil Velikov
2002-01-31 2:25 ` Andrea Arcangeli [this message]
2002-01-31 22:26 ` Horst von Brand
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=20020131032540.W1309@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=velco@fadata.bg \
/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