From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfs: rename "linux-2.6" subdirectory to be simply "linux"
Date: Fri, 22 Jul 2011 10:58:42 -0400 [thread overview]
Message-ID: <20110722145842.GA15962@infradead.org> (raw)
In-Reply-To: <1311346434.2771.17.camel@doink>
On Fri, Jul 22, 2011 at 09:53:54AM -0500, Alex Elder wrote:
> On Fri, 2011-07-22 at 10:34 -0400, Christoph Hellwig wrote:
> > Actually it should just go away. It's a leftover from when we had
> > code for Linux 2.4 and Linux 2.6 in the same ptools repository.
>
> So this is an admission that XFS has gone from an
> Irix-only to a Linux-only filesystem? We have
> strayed from it but I think there is value in
> trying to separate the core platform-independent
> part of the code from the part that interfaces
> with the OS environment.
It's not Linux only, but very centered around Linux APIs. We still
have a low-level layer that only uses library-functins like sorting
helpers, trees, etc from the generic kernel, and a higher level that
fully interacts with it. This seems like a useful abstraction to me,
and I'd like to keep it that way (nevermind that we really have to
because of libxfs in xfsprogs). But that border is nowhere near the
linux-2.6 directory split, and much better done using a comment in
the makefile explaining which files are shared with libxfs. That's
what I was planning to do for my move pull request.
Note that currently the shared code doesn't even perfectly align to
files, making the libxfs resync harder than nessecary, but that's
also something on my mid-term todo list.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-22 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 18:04 [PATCH, RFC] xfs: rename "linux-2.6" subdirectory to be simply "linux" Alex Elder
2011-07-22 14:34 ` Christoph Hellwig
2011-07-22 14:53 ` Alex Elder
2011-07-22 14:58 ` 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=20110722145842.GA15962@infradead.org \
--to=hch@infradead.org \
--cc=aelder@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