From: "David S. Miller" <davem@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH] swp_entry_t vs. swap pte.
Date: Wed, 24 Mar 2004 14:04:19 -0800 [thread overview]
Message-ID: <20040324140419.29ec6a69.davem@redhat.com> (raw)
In-Reply-To: <20040324180939.GA2599@mschwid3.boeblingen.de.ibm.com>
On Wed, 24 Mar 2004 19:09:39 +0100
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> I created a patch that should fix the problem. It uses
>
> swp_type(pte_to_swp_entry(swp_entry_to_pte(swp_entry(~0UL,0))))
>
> to find the highest possible swap type number and
>
> swp_offset(pte_to_swp_entry(swp_entry_to_pte(swp_entry(0,~0UL))))
>
> to find the highest possible swap offset. This should work with the
> existing __swp_entry/__swp_type/__swp_offset definitions for all
> architectures except for s390 because I've added a BUG_ON in
> __swp_entry if the created swap pte is dubious. Oh, well.
This looks fine to me Martin.
I'm not going to fiddle with the swp bit fields on sparc64, the
offset range is huge enough :-)
next prev parent reply other threads:[~2004-03-24 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 18:09 [PATCH] swp_entry_t vs. swap pte Martin Schwidefsky
2004-03-24 22:04 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 13:02 Martin Schwidefsky
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=20040324140419.29ec6a69.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.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