public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/7] xfs: fix min bufsize bugs in two places
Date: Thu, 25 Mar 2010 09:23:34 -0500	[thread overview]
Message-ID: <1269527014.2523.5.camel@doink> (raw)
In-Reply-To: <20100320164249.GB31444@infradead.org>

On Sat, 2010-03-20 at 12:42 -0400, Christoph Hellwig wrote:
> > +/* Number of basic blocks in a log sector */
> > +#define xlog_sectbb(log) (1 << (log)->l_sectbb_log)
> 
> Looking at all uses of (log)->l_sectbb_log I wonder if we should
> bother storing this in the log structure in this form, or rather
> as the multipler of the basic block size, ala l_sectsize.  All the

I agree, and I was sort of headed in that direction.  I have
more work in this file that eventually will lead to some larger
scale (algorithmic) simplification.  But for now I'm starting
small.

> 	if (log->l_sectbb_log) {
> 
> checks would just become
> 
> 	if (log->l_sectsize > 1) {
> 
> and the xlog_find_verify_cycle/xlog_write_log_records checks
> would also be a natural
> 
> 	if (bufblks < log->l_sectsize)

I'll attack this in a later patch.

> The comments added are defintively useful, btw.

Thanks, I felt they were necessary.  More to come.

I got "looks good" from you on all but this patch,
and numbers 5 and 7 in the series.  Is this one OK,
and do you plan to review those other two?

					-Alex

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-03-25 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 22:53 [PATCH 2/7] xfs: fix min bufsize bugs in two places Alex Elder
2010-03-20 16:42 ` Christoph Hellwig
2010-03-25 14:23   ` Alex Elder [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=1269527014.2523.5.camel@doink \
    --to=aelder@sgi.com \
    --cc=hch@infradead.org \
    --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