From: Dave Chinner <david@fromorbit.com>
To: Bill Kendall <wkendall@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump support for 64K page size
Date: Thu, 15 Jan 2009 09:48:57 +1100 [thread overview]
Message-ID: <20090114224857.GA8071@disturbed> (raw)
In-Reply-To: <4967A73E.9020907@sgi.com>
On Fri, Jan 09, 2009 at 01:36:30PM -0600, Bill Kendall wrote:
> Dave Chinner wrote:
> > BTW, these changes are the *exact* patches I sent back in March.
> > I note that the change logs from those patches have been dropped
> > on the floor. i.e.:
>
> Right, only difference is that I removed the asserts rather than
> just having them commented out. In my determination the asserts
> are totally bogus -- there isn't a dependency on the system's
> page size in the inomap code.
.....
> The inomap code uses xfsdump's PGSZ variable, which is fixed at 4K.
> There's no dependency here on the system's actual page size. I was
> able to dump and then restore on a system with a different page size.
Ok, that looks fine. however, there is a dependency that HNKSZ >=
PGSZ, right? And that is currently hardwired to (4 * PGSZ)?
And given that the intent of the PGSZ was to be made variable at
some point, isn't this really trying to ensure that HNKSZ is always
greater than the PGSZ the program was built with?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-14 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 15:10 [PATCH] xfsdump support for 64K page size Bill Kendall
2009-01-08 2:19 ` Mark Goodwin
2009-01-08 15:37 ` Christoph Hellwig
2009-01-08 22:28 ` Dave Chinner
2009-01-08 23:02 ` Eric Sandeen
2009-01-09 19:36 ` Bill Kendall
2009-01-09 19:41 ` Christoph Hellwig
2009-01-14 22:48 ` Dave Chinner [this message]
2009-01-15 18:59 ` Bill Kendall
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=20090114224857.GA8071@disturbed \
--to=david@fromorbit.com \
--cc=wkendall@sgi.com \
--cc=xfs-dev@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