From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John Marvin <jsm@udlkern.fc.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [akpm@digeo.com: arch changes for file-offset-in-pte's]
Date: Mon, 24 Mar 2003 14:19:00 -0500 [thread overview]
Message-ID: <20030324191900.GA6324@systemhalted> (raw)
In-Reply-To: <200303241328.GAA02336@udlkern.fc.hp.com>
> Another possibility would be to split out the SWP_TYPE, SWP_OFFSET
> and SWP_ENTRY macros in order to have a 32 bit kernel version and a
> 64 bit kernel version. Then we could go with 16 swap devices for the
> 32 bit kernel and even increase the number of swap devices for the
> 64 bit kernel, since we have a huge number of bits for the offset.
My $0.02
a) Keep the swap size the same, and reduce the number of entries.
= Offers better compatiblity in most situations
b) Split the macro's, keeping the swap size the same, and increase
the number of possible devices.
= Offers size consistency, and benefits to 64-bit kernels.
c.
next prev parent reply other threads:[~2003-03-24 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 13:28 [parisc-linux] [akpm@digeo.com: arch changes for file-offset-in-pte's] John Marvin
2003-03-24 19:19 ` Carlos O'Donell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-22 1:20 Matthew Wilcox
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=20030324191900.GA6324@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@lists.parisc-linux.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