From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/5] xfs: factor free block index lookup from xfs_dir2_node_addname_int()
Date: Fri, 26 Oct 2018 21:49:06 +1100 [thread overview]
Message-ID: <20181026104906.GE19305@dastard> (raw)
In-Reply-To: <20181026094805.GB29302@infradead.org>
On Fri, Oct 26, 2018 at 02:48:05AM -0700, Christoph Hellwig wrote:
> > +/*
> > + * Add the data entry for a node-format directory name addition.
> > + * The leaf entry is added in xfs_dir2_leafn_add.
> > + * We may enter with a freespace block that the lookup found.
> > + */
> > +static int /* error */
> > +xfs_dir2_node_addname_int(
> > + xfs_da_args_t *args, /* operation arguments */
> > + xfs_da_state_blk_t *fblk) /* optional freespace block */
> > +{
> > + xfs_dir2_data_hdr_t *hdr; /* data block header */
> > + xfs_dir2_db_t dbno; /* data block number */
> > + struct xfs_buf *dbp; /* data block buffer */
> > + xfs_dir2_data_entry_t *dep; /* data entry pointer */
> > + xfs_inode_t *dp; /* incore directory inode */
> > + xfs_dir2_data_unused_t *dup; /* data unused entry pointer */
> > + int error; /* error return value */
> > + struct xfs_buf *fbp; /* freespace buffer */
> > + int findex; /* freespace entry index */
> > + xfs_dir2_free_t *free=NULL; /* freespace block structure */
> > + int length; /* length of the new entry */
> > + int logfree = 0; /* need to log free entry */
> > + int needlog = 0; /* need to log data header */
> > + int needscan = 0; /* need to rescan data frees */
> > + __be16 *tagp; /* data entry tag pointer */
> > + xfs_trans_t *tp; /* transaction pointer */
> > + __be16 *bests;
> > + struct xfs_dir2_data_free *bf;
> > + xfs_dir2_data_aoff_t aoff;
> > +
> > + dp = args->dp;
> > + tp = args->trans;
> > + length = dp->d_ops->data_entsize(args->namelen);
>
> Can you remove the use of typedefs and move the trivial initializers
> to the declaration like you've done for the new helpers here?
I didn't touch this code in xfs_dir2_node_addname_int()
except to remove variables that are now in the new function.
What you see here is a result of the diff generator deciding to
replace the original declaration of this function with the new
function I added, and so it looks like I add this code when in fact
I didn't...
I'll go back an fixup up more code.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-10-26 19:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 22:57 [PATCH 0/5] xfs: speed up large directory modifications Dave Chinner
2018-10-24 22:57 ` [PATCH 1/5] xfs: move xfs_dir2_addname() Dave Chinner
2018-10-26 9:24 ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 2/5] xfs: factor data block addition from xfs_dir2_node_addname_int() Dave Chinner
2018-10-26 9:45 ` Christoph Hellwig
2018-10-26 10:52 ` Dave Chinner
2018-10-26 12:01 ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 3/5] xfs: factor free block index lookup " Dave Chinner
2018-10-26 9:48 ` Christoph Hellwig
2018-10-26 10:49 ` Dave Chinner [this message]
2018-10-24 22:57 ` [PATCH 4/5] xfs: speed up directory bestfree block scanning Dave Chinner
2018-10-26 10:24 ` Christoph Hellwig
2018-10-26 10:58 ` Dave Chinner
2018-10-26 11:56 ` Christoph Hellwig
2018-10-26 12:12 ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 5/5] xfs: reverse search directory freespace indexes Dave Chinner
2018-10-26 12:14 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 6:30 [PATCH V2 0/5] xfs: speed up large directory modifications Dave Chinner
2019-08-29 6:30 ` [PATCH 3/5] xfs: factor free block index lookup from xfs_dir2_node_addname_int() Dave Chinner
2019-08-29 8:10 ` Christoph Hellwig
2019-08-29 8:35 ` Dave Chinner
2019-08-29 10:47 [PATCH v3 0/5] xfs: speed up large directory modifications Dave Chinner
2019-08-29 10:47 ` [PATCH 3/5] xfs: factor free block index lookup from xfs_dir2_node_addname_int() Dave Chinner
2019-08-29 21:07 ` Darrick J. Wong
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=20181026104906.GE19305@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/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