From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@namesys.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Linus Torvalds <torvalds@transmeta.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org,
reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] Re: Block I/O Enchancements, 2.5.1-pre2
Date: Sat, 01 Dec 2001 12:31:51 +0300 [thread overview]
Message-ID: <3C08A387.90303@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111271933100.1195-100000@penguin.transmeta.com> <E169dGg-0000iO-00@starship.berlin> <3C0779BD.7090604@namesys.com> <15367.32910.275973.287742@laputa.namesys.com>
Nikita Danilov wrote:
>Hans Reiser writes:
>
>
>Having 64 bit inode numbers is good, but we *can* live without them:
>currently inode hash table can store inodes with identical inode
>numbers, provided they can be distinguished by find_actor. Inode numbers
>are just first fast guess during table scan, if they coincide,
>find_actor is used.
>
Nikita is entirely correct, 32 bits of inode number hash is plenty.
64k blocks remain a solution whose potential drain on memory bandwidth
worries me.
Hans
next prev parent reply other threads:[~2001-12-01 9:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:44 2.5.1-pre2 does not compile f5ibh
2001-11-27 20:50 ` Linus Torvalds
2001-11-27 22:02 ` Paul Mackerras
2001-11-28 1:04 ` Linus Torvalds
2001-11-28 1:34 ` Block I/O Enchancements, 2.5.1-pre2 Jeff V. Merkey
2001-11-28 1:45 ` Jeff Garzik
2001-11-28 1:55 ` Jeff V. Merkey
2001-11-28 2:32 ` Jeff Garzik
2001-11-28 3:38 ` Linus Torvalds
2001-11-30 2:19 ` Daniel Phillips
2001-11-30 12:21 ` Hans Reiser
[not found] ` <15367.32910.275973.287742@laputa.namesys.com>
2001-12-01 9:31 ` Hans Reiser [this message]
2001-11-28 10:17 ` Martin Dalecki
2001-11-28 13:35 ` Jens Axboe
2001-11-28 17:29 ` Jeff Merkey
2001-11-28 6:58 ` 2.5.1-pre2 does not compile Jens Axboe
2001-11-28 12:20 ` bio write-up (was: Re: 2.5.1-pre2 does not compile) Jens Axboe
2001-11-28 23:31 ` 2.5.1-pre2 bio offset by one error in VIA IDE Anton Altaparmakov
2001-11-28 23:55 ` Andreas Dilger
2001-11-29 1:07 ` Anton Altaparmakov
2001-11-30 1:53 ` 2.5.1-pre2 does not compile Daniel Phillips
2001-11-27 22:09 ` Christoph Hellwig
2001-11-27 22:22 ` onboard ethernet/sound on Soyo SY-K7V? Dax Kelson
2001-11-27 22:47 ` François Cami
2001-11-27 22:57 ` Jeff Garzik
2001-11-27 22:29 ` 2.5.1-pre2 does not compile Robert Love
2001-11-28 0:29 ` Linus Torvalds
2001-11-28 12:55 ` Christoph Hellwig
2001-11-28 16:26 ` Andreas Dilger
2001-11-28 16:42 ` Christoph Hellwig
2001-11-28 16:39 ` Martin Dalecki
2001-11-28 17:27 ` Andreas Dilger
2001-11-28 0:40 ` Andre Hedrick
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=3C08A387.90303@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@namesys.com \
--cc=axboe@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=reiserfs-dev@namesys.com \
--cc=torvalds@transmeta.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