From: Christoph Hellwig <hch@infradead.org>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW] Update kernel headers to compile in userspace (libxfs)
Date: Tue, 29 Jul 2008 00:19:39 -0400 [thread overview]
Message-ID: <20080729041939.GA7232@infradead.org> (raw)
In-Reply-To: <op.ue07o7wt3jf8g2@pc-bnaujok.melbourne.sgi.com>
On Tue, Jul 29, 2008 at 12:25:45PM +1000, Barry Naujok wrote:
> +#ifdef __KERNEL__
> atomic_t pagf_fstrms; /* # of filestreams active in this AG */
>
> int pag_ici_init; /* incore inode cache initialised */
> rwlock_t pag_ici_lock; /* incore inode lock */
> struct radix_tree_root pag_ici_root; /* incore inode cache root */
> +#endif
I gues this does indeed not make much sense in userspace.
> +#ifdef __KERNEL__
> extern int xfs_dir2_block_getdents(struct xfs_inode *dp, void *dirent,
> xfs_off_t *offset, filldir_t filldir);
> +#endif
Instead of all these ifdefs in the dir code wouldn't it be better
to just provide a filldir_t in userspace? getdents into a user
formatted buffers sounds at least like a theoretically useful
functionality for libxfs.
> Index: 2.6.x-xfs/fs/xfs/xfs_inode_item.h
> ===================================================================
> --- 2.6.x-xfs.orig/fs/xfs/xfs_inode_item.h
> +++ 2.6.x-xfs/fs/xfs/xfs_inode_item.h
> @@ -168,6 +168,8 @@ static inline int xfs_ilog_fext(int w)
> return (w == XFS_DATA_FORK ? XFS_ILOG_DEXT : XFS_ILOG_AEXT);
> }
>
> +#ifdef __KERNEL__
> +
> static inline int xfs_inode_clean(xfs_inode_t *ip)
> {
> return (!ip->i_itemp ||
> @@ -175,9 +177,6 @@ static inline int xfs_inode_clean(xfs_in
> !ip->i_update_core;
> }
>
> -
> -#ifdef __KERNEL__
> -
> extern void xfs_inode_item_init(struct xfs_inode *, struct xfs_mount *);
> extern void xfs_inode_item_destroy(struct xfs_inode *);
> extern void xfs_iflush_done(struct xfs_buf *, xfs_inode_log_item_t *);
Makes sense, too.
prev parent reply other threads:[~2008-07-29 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 2:25 [REVIEW] Update kernel headers to compile in userspace (libxfs) Barry Naujok
2008-07-29 4:19 ` 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=20080729041939.GA7232@infradead.org \
--to=hch@infradead.org \
--cc=bnaujok@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