From: Russell Cattelan <cattelan@thebarn.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] kill bhv_vnode_t
Date: Wed, 23 Jul 2008 18:58:58 -0500 [thread overview]
Message-ID: <4887C5C2.7080500@thebarn.com> (raw)
In-Reply-To: <20080723215721.GA11049@lst.de>
Christoph Hellwig wrote:
> On Wed, Jul 23, 2008 at 04:53:17PM -0500, Russell Cattelan wrote:
>
>> Christoph Hellwig wrote:
>>
>>> Dave complained today that the fate of bhv_vnode_t isn't entirely clear
>>> yet, so I've prepared these two patches to kill it in a minimally
>>> invasive way. While it causes churn in a lot of areas it does not
>>> affect the generated code at all.
>>>
>>>
>>>
>> I know a bunch of stuff has gone in that is not very portable, which is
>> fine since
>> they can be dealt with individually since they are not that intrusive.
>>
>> Changing bhv_vnode_t to struct inode throughout the code is a pretty big
>> change and would be a major pain to work around.
>>
>
> Have you actually looed at the patches? The only places where we use
> struct inode outside of linux-2.6/ are:
>
> - xfs_finish_reclaim:
>
> Distangles the xfs_inode from Linux inode. Per defintion
> OS-specific.
>
> - xfs_sync_inodes:
>
> Sync code that is quite OS specific. Dave will move it
> to linux-2.6/ pretty soon.
>
> - quota/xfs_qm_syscalls.c:
>
> Similar sync code.
>
> - xfs_acl.c:
>
> ACL code with some OS dependencies, and pretty dead with my
> pending patch to use the generic ACL code.
>
> And no, it's not actually a big change.
>
>
I guess it's not that big of a change anymore.
I really need to find some time and get fbsd synced up with the latest
xfs code.
-Russell
prev parent reply other threads:[~2008-07-23 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 21:47 [PATCH 0/2] kill bhv_vnode_t Christoph Hellwig
2008-07-23 21:53 ` Russell Cattelan
2008-07-23 21:57 ` Christoph Hellwig
2008-07-23 23:58 ` Russell Cattelan [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=4887C5C2.7080500@thebarn.com \
--to=cattelan@thebarn.com \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.