From: Andrew Morton <akpm@osdl.org>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: i_blksize
Date: Tue, 5 Aug 2003 10:50:06 -0700 [thread overview]
Message-ID: <20030805105006.2769e44a.akpm@osdl.org> (raw)
In-Reply-To: <UTC200308051627.h75GR7J08241.aeb@smtp.cwi.nl>
Andries.Brouwer@cwi.nl wrote:
>
> > Looks like I got myself confused
>
> Yes. But nevertheless, now that you brought this up,
> we might consider throwing out i_blksize.
>
> I am not aware of anybody who actually uses this to give
> per-file advice. So, it could be in the superblock.
I suppose so. reiserfs plays with it.
I can't really see that anyone would want to set the I/O size hint on a
per-inode basis, especially as the readahead and writebehind code will
cheerfully ignore it.
> Any objections?
I don't think it's worth fiddling with at this time, really.
> If sizeof(struct inode) decreases by 1% then we can keep 1% more inodes.
>
> That reminds me - I threw out i_dev and i_cdev, but Al reintroduced i_cdev.
> We should do as some comment says and make a union with i_bdev and i_pipe.
> Another 8 bytes gone.
Well all the inode slab caches are using SLAB_HWCACHE_ALIGN at present, so
it's a little moot. Especially on a pentium4-compiled kernel.
But I expect most distributed 2.6 kernels will be pII or pIII-compiled.
Let's look:
SMP:
sizeof(struct ext2_inode_info) = 0x1d0
sizeof(struct ext3_inode_info) = 0x1e0
Both of these pack eight-per-page. Need to get them to 0x1c4 (and remove
SLAB_HWCACHE_ALIGN) to get to nine-per-page.
UP:
sizeof(struct ext3_inode_info) = 0x1c4 (whew!)
sizeof(struct ext2_inode_info) = 0x1b4
So for these filesystems at least, we need to remove SLAB_HWCACHE_ALIGN and
we will get a 12% improvement in packing density on uniprocessor.
unionification of i_[bcp]dev sounds like a good idea to give us a little
margin there.
next prev parent reply other threads:[~2003-08-05 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 16:27 i_blksize Andries.Brouwer
2003-08-05 17:50 ` Andrew Morton [this message]
2003-08-05 18:09 ` i_blksize Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 19:48 i_blksize Andries.Brouwer
2003-08-05 9:20 i_blksize Andries.Brouwer
2003-08-05 15:55 ` i_blksize Andrew Morton
2003-08-04 2:03 do_div considered harmful Andries.Brouwer
2003-08-04 2:29 ` Andrew Morton
2003-08-05 2:58 ` i_blksize Andries Brouwer
2003-08-05 6:10 ` i_blksize Andrew Morton
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=20030805105006.2769e44a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).