From: Daniel Phillips <phillips@arcor.de>
To: Christoph Hellwig <hch@lst.de>, marcelo@conectiva.com.br
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rework inode allocation to allow filesystems more control
Date: Mon, 16 Sep 2002 07:55:30 +0200 [thread overview]
Message-ID: <E17qor4-0000HW-00@starship> (raw)
In-Reply-To: <20020911145557.A13949@lst.de>
On Wednesday 11 September 2002 14:55, Christoph Hellwig wrote:
> This patch adds ->alloc_inode and ->destroy_inode super operations to
> allow the filesystem control the allocation of struct inode, e.g. to
> have it's private inode and the VFS one n the same slab cache.
>
> This 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.
How about a credit for the original author/designer? Yes, that was me.
--
Daniel
prev parent reply other threads:[~2002-09-16 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 12:55 Christoph Hellwig
2002-09-16 5:55 ` Daniel Phillips [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=E17qor4-0000HW-00@starship \
--to=phillips@arcor.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=viro@math.psu.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
all inboxes | Powered by JetHome®