| To: | Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH 07/15] refactor xfs_btree_readahead |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Fri, 25 Jul 2008 06:14:18 +0200 |
| In-reply-to: | <20080724233655.GH15438@disturbed> |
| References: | <20080723200859.GH7401@xxxxxx> <20080724233655.GH15438@disturbed> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Fri, Jul 25, 2008 at 09:36:55AM +1000, Dave Chinner wrote: > On Wed, Jul 23, 2008 at 10:08:59PM +0200, Christoph Hellwig wrote: > > From: Dave Chinner <dgc@xxxxxxx> > > Can i review my own code? ;) Sure.. > > +STATIC int > > +xfs_btree_reada_corel( > > I've been wondering if this is the best naming convention - > appending a single s or l to indicate short or long btree ops. > Perhaps this would be better as xfs_btree_readahead_short() and > xfs_btree_readahead_long(), esp. as we dropped the 'core' from > the caller to make it xfs_btree_readahead(). > > Otherwise it looks good. I'll see if I can find a saner name. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2/4] XFS: Use the inode tree for finding dirty inodes, Mark Goodwin |
|---|---|
| Next by Date: | Re: [PATCH] use generic posix ACL code, enable ACL caching, Niv Sardi |
| Previous by Thread: | Re: [PATCH 07/15] refactor xfs_btree_readahead, Dave Chinner |
| Next by Thread: | Re: [PATCH 07/15] refactor xfs_btree_readahead, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |