From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] xfs: drop dmapi hooks
Date: Fri, 21 May 2010 16:36:17 -0500 [thread overview]
Message-ID: <4BF6FCD1.10805@sandeen.net> (raw)
In-Reply-To: <20100510140823.GA16540@infradead.org>
Christoph Hellwig wrote:
> Dmapi support was never merged upstream, but we still have a lot of hooks
> bloating XFS for it, all over the fast pathes of the filesystem.
>
> This patch drops over 700 lines of dmapi overhead. If we'll ever get HSM
> support in mainline at least the namespace events can be done much saner
> in the VFS instead of the individual filesystem, so it's not like this
> is much help for future work.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
yeah, probably about time.
There is a fair bit of dmapi crumbs left though:
[sandeen@sandeen xfs]$ grep -ri dmapi * | wc -l
63
so I think this patch can go further toward its goal...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-21 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 14:08 [PATCH 1/2] xfs: drop dmapi hooks Christoph Hellwig
2010-05-21 21:36 ` Eric Sandeen [this message]
2010-05-25 9:45 ` [PATCH 1/2 v2] " Christoph Hellwig
2010-05-26 6:12 ` Dave Chinner
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=4BF6FCD1.10805@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