public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
	xfs-oss <xfs@oss.sgi.com>
Subject: Re: Review: Multi-File Data Streams V2
Date: Mon, 18 Jun 2007 11:47:31 +1000	[thread overview]
Message-ID: <20070618014731.GV86004887@sgi.com> (raw)
In-Reply-To: <20070616203851.GA7817@infradead.org>

On Sat, Jun 16, 2007 at 09:38:51PM +0100, Christoph Hellwig wrote:
> Thanks, this version looks a lot better now.
> 
> The pip checks in xfs_inode.c are still in, but I'm pretty sure they're
> not nessecary, and even if they were nessecary they'd need a good comment
> explaining why.

Because quota inodes don't have a parent and doing filestreams stuff
on quota inodes causes all sorts on problems.

I forgot to split that patch out like you asked last time. Will
now be patch 2, because without this fix we get extra references on
the quota inodes that never get removed and hence busy inodes
after unmount problems....

> The patch still hooks into xfs_close despite your comment that you
> updated it for the removal of it.

<sigh>

That's because it is moved in the xfs_close removal patch later in
my series.  I'll move it.

> I still strongly believe the mru cache should not be inside xfs.  It's
> a completely generic library function and should go into lib/ so it's
> available to all of the kernel.  That means it'll need some codingstyle
> updates and proper kerneldoc comments, though.

And like I said last time: I don't disagree with you.

However: I'm not going to hold back the filestreams code for this.
Doing janitorial work like this is a complete and utter waste of
my time and it does nothing to improve the code right now. I'll
happily accept patches that move this code to lib/ if someone goes
and does it before I find the cycles to be able to do it.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-06-18 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13  4:16 Review: Multi-File Data Streams V2 David Chinner
2007-06-16 20:38 ` Christoph Hellwig
2007-06-18  1:47   ` David Chinner [this message]
2007-06-22  8:44 ` Timothy Shimmin
2007-06-25  3:53   ` David Chinner
2007-06-26 12:16     ` Tim Shimmin

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=20070618014731.GV86004887@sgi.com \
    --to=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=xfs-dev@sgi.com \
    --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