From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 4/5] xfs: remove m_litino
Date: Fri, 20 Mar 2009 22:57:32 -0500 [thread overview]
Message-ID: <49C465AC.3010809@sandeen.net> (raw)
In-Reply-To: <20090318094132.224487000@bombadil.infradead.org>
Christoph Hellwig wrote:
> With the upcoming v3 inodes the inode data/attr area size needs to be
> calculated for each specific inode, so we can't cache it in the superblock
> anymore.
hm, ok, but why do this now?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-21 3:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 9:41 [PATCH 0/5] A couple more patches for 2.6.30 Christoph Hellwig
2009-03-18 9:41 ` [PATCH 1/5] xfs: cleanup uuid handling Christoph Hellwig
2009-03-29 7:45 ` Christoph Hellwig
2009-03-30 6:06 ` Felix Blyakher
2009-03-18 9:41 ` [PATCH 2/5] xfs: kill mutex_t typedef Christoph Hellwig
2009-03-21 3:51 ` Eric Sandeen
2009-03-26 22:31 ` Felix Blyakher
2009-03-18 9:41 ` [PATCH 3/5] xfs: kill ino64 mount option Christoph Hellwig
2009-03-21 3:54 ` Eric Sandeen
2009-03-21 20:08 ` Christoph Hellwig
2009-03-21 22:12 ` Eric Sandeen
2009-03-24 8:30 ` Dave Chinner
2009-03-24 13:11 ` Eric Sandeen
2009-03-26 22:37 ` Felix Blyakher
2009-03-18 9:41 ` [PATCH 4/5] xfs: remove m_litino Christoph Hellwig
2009-03-21 3:57 ` Eric Sandeen [this message]
2009-03-21 20:09 ` Christoph Hellwig
2009-03-26 22:41 ` Felix Blyakher
2009-03-29 7:48 ` Christoph Hellwig
2009-03-18 9:41 ` [PATCH 5/5] xfs: remove m_attroffset Christoph Hellwig
2009-03-26 19:42 ` Josef 'Jeff' Sipek
2009-03-29 7:50 ` Christoph Hellwig
2009-04-06 22:11 ` Felix Blyakher
2009-04-07 16:01 ` Christoph Hellwig
2009-03-29 9:28 ` [PATCH 0/5] A couple more patches for 2.6.30 Christoph Hellwig
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=49C465AC.3010809@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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