From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH] ext4: Don't use 'struct dentry' for internal lookups
Date: Sun, 21 Sep 2008 16:17:08 -0400 [thread overview]
Message-ID: <20080921201708.GA29476@infradead.org> (raw)
In-Reply-To: <E1KhEil-0004s7-Ve@closure.thunk.org>
On Sat, Sep 20, 2008 at 10:30:47PM -0400, Theodore Ts'o wrote:
> This is a port of a patch from Linus which fixes a 200+ byte stack
> usage problem in ext4_get_parent().
>
> It's more efficient to pass down only the actual parts of the dentry
> that matter: the parent inode and the name, instead of allocating a
> struct dentry on the stack.
Al had a variant of this in the vfs queue for a while.
prev parent reply other threads:[~2008-09-21 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 2:30 [PATCH] ext4: Don't use 'struct dentry' for internal lookups Theodore Ts'o
2008-09-21 19:48 ` Linus Torvalds
2008-09-21 20:17 ` Christoph Hellwig [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=20080921201708.GA29476@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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