From: "H. Peter Anvin" <hpa@zytor.com>
To: Anton Blanchard <anton@samba.org>
Cc: David Miller <davem@davemloft.net>,
hch@infradead.org, arjan@infradead.org, zippel@linux-m68k.org,
dmlb2000@gmail.com, linux-kernel@vger.kernel.org,
gdb@sourceware.org
Subject: Re: PAGE_SIZE Availability Inconsistency
Date: Tue, 20 Mar 2007 19:48:10 -0700 [thread overview]
Message-ID: <46009CEA.1050206@zytor.com> (raw)
In-Reply-To: <20070321021202.GA11745@kryten>
Anton Blanchard wrote:
> Hi,
>
>> The advantage would be that it wouldn't require a v3 for platforms for
>> which MIN_PAGE_SIZE == PAGE_SIZE, which accounts for a very large
>> percentage of systems.
>>
>> You still have to look for the darn magic in two places, so there is no
>> reason for it to be different.
>
> The problem is if you can hit in two places then what PAGE_SIZE should
> you use to size the contents of the swap header while remaining backward
> compatible.
>
> Im leaning towards Dave suggestion of creating a clean v3 swap header.
>
Changing the header format doesn't make *ANY* difference whatsoever.
You have to write two copies of the swap header, and the kernel should
check for a header at MIN_PAGE_SIZE first and then at PAGE_SIZE.
If there are fields (other than position) in the v2 swap header that are
dependent on PAGE_SIZE, then the copy at MIN_PAGE_SIZE should be sized
using MIN_PAGE_SIZE, and the copy at PAGE_SIZE should be sized at
PAGE_SIZE. It's that simple.
Creating a new format will not help that one iota, and will create
gratuitous incompatiblity for the very common case of PAGE_SIZE ==
MIN_PAGE_SIZE.
-hpa
-hpa
next prev parent reply other threads:[~2007-03-21 2:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 23:55 PAGE_SIZE Availability Inconsistency David Brown
2007-03-05 23:59 ` Eric Dumazet
2007-03-06 0:01 ` Randy Dunlap
2007-03-06 0:03 ` David Miller
2007-03-06 0:04 ` David Brown
2007-03-06 0:26 ` David Miller
2007-03-06 2:21 ` H. Peter Anvin
2007-03-08 21:08 ` Avi Kivity
2007-03-08 22:21 ` H. Peter Anvin
2007-03-19 19:39 ` Eric W. Biederman
2007-03-06 9:29 ` Christoph Hellwig
2007-03-08 2:18 ` Roman Zippel
2007-03-08 5:28 ` David Brown
2007-03-08 8:32 ` Christoph Hellwig
2007-03-08 9:00 ` Christoph Hellwig
2007-03-08 15:53 ` Arjan van de Ven
2007-03-08 16:08 ` Christoph Hellwig
2007-03-08 16:21 ` Daniel Jacobowitz
2007-03-08 17:05 ` H. Peter Anvin
2007-03-08 17:12 ` Christoph Hellwig
2007-03-08 17:57 ` Anton Blanchard
2007-03-08 18:04 ` H. Peter Anvin
2007-03-08 21:42 ` Anton Blanchard
2007-03-08 21:46 ` Anton Blanchard
2007-03-08 21:48 ` David Miller
2007-03-09 2:43 ` Anton Blanchard
2007-03-09 4:18 ` H. Peter Anvin
2007-03-09 4:27 ` David Miller
2007-03-09 4:31 ` H. Peter Anvin
2007-03-09 4:36 ` David Miller
2007-03-21 2:12 ` Anton Blanchard
2007-03-21 2:48 ` H. Peter Anvin [this message]
2007-03-08 22:22 ` H. Peter Anvin
2007-03-08 21:03 ` David Brown
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=46009CEA.1050206@zytor.com \
--to=hpa@zytor.com \
--cc=anton@samba.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=dmlb2000@gmail.com \
--cc=gdb@sourceware.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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