From: Jeff Garzik <jeff@garzik.org>
To: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Slimming down struct inode
Date: Sat, 10 Jun 2006 11:06:13 -0400 [thread overview]
Message-ID: <448ADFE5.4030008@garzik.org> (raw)
In-Reply-To: <20060610110335.GA7959@irc.pl>
Tomasz Torcz wrote:
> On Fri, Jun 09, 2006 at 07:50:08PM -0400, Theodore Ts'o wrote:
>> So without further ado, here are some ideas of ways that we can slim
>> down struct inode:
>>
>> 1) Move i_blksize (optimal size for I/O, reported by the stat system
>> call). Is there any reason why this needs to be per-inode, instead
>> of per-filesystem?
>>
>> 2) Move i_blkbits (blocksize for doing direct I/O in bits) to struct
>> super. Again, why is this per-inode?
>
> ZFS filesystem uses dynamic, per-file blocksizes. Some Linux
> filesystem may implement something like this in order to be called
> "modern".
Yep, Sun stole my buckets idea <j/k> I think ZFS calls them
"meta-slabs" or somesuch.
See what I posted in the 'continuous inodes' sub-thread.
Jeff
next prev parent reply other threads:[~2006-06-10 15:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 23:50 [RFC] Slimming down struct inode Theodore Ts'o
2006-06-10 0:24 ` Bernd Eckenfels
2006-06-10 1:27 ` Al Viro
2006-06-10 1:56 ` Theodore Tso
2006-06-10 6:24 ` Stefan Richter
2006-06-10 10:48 ` Jan Engelhardt
2006-06-10 15:04 ` Jeff Garzik
2006-06-13 4:35 ` Nathan Scott
2006-06-13 4:32 ` Nathan Scott
2006-06-13 14:00 ` Avi Kivity
2006-06-13 17:44 ` Theodore Tso
2006-06-13 18:08 ` Avi Kivity
2006-06-13 20:10 ` Jan Engelhardt
2006-06-13 20:25 ` Avi Kivity
2006-06-13 22:41 ` Nathan Scott
2006-06-14 10:29 ` Nikita Danilov
2006-06-14 21:50 ` Nathan Scott
2006-06-15 5:49 ` Theodore Tso
2006-06-15 7:01 ` Nathan Scott
2006-06-15 8:46 ` Brian F. G. Bidulock
2006-06-15 10:20 ` Nathan Scott
2006-06-14 23:27 ` Jan Engelhardt
2006-06-15 10:09 ` Nikita Danilov
2006-06-10 11:03 ` Tomasz Torcz
2006-06-10 15:06 ` Jeff Garzik [this message]
2006-06-15 0:16 ` Brian F. G. Bidulock
2006-06-15 4:43 ` Theodore Tso
2006-06-15 8:27 ` Brian F. G. Bidulock
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=448ADFE5.4030008@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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