From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@sgi.com>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][5th RESENT] backport 2.5 inode allocation changes
Date: Fri, 27 Sep 2002 15:10:45 -0400 [thread overview]
Message-ID: <3D94AD35.4050505@pobox.com> (raw)
In-Reply-To: 20020927212707.B4733@sgi.com
Christoph Hellwig wrote:
> It allows to break worst-offenders like NFS out of the big inode union
> and make VM balancing better by wasting less ram for inodes. It also
> speedups filesystems that don't want to touch that union in struct
> inode, like JFS, XFS or FreeVxFS (once switched over). It is a straight
> backport from Al's code in 2.5 and has proven stable in Red Hat's
> recent beta releases (limbo, null). Al has ACKed my patch submission.
>
> Credits go to Daniel Phillips for the initial design.
>
> NOTE: you want my b_inode removal patch applied before this one.
IMO this patch (and b_inode before it) look ok...
but I have a feeling we will have a public disagreement over actually
shrinking the size of the inode struct... [but this patch does not do
that, so IMO it's fine]
prev parent reply other threads:[~2002-09-27 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 1:27 [PATCH][5th RESENT] backport 2.5 inode allocation changes Christoph Hellwig
2002-09-27 19:10 ` Jeff Garzik [this message]
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=3D94AD35.4050505@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.