From: "David S. Miller" <davem@redhat.com>
To: bruce.holzrichter@monster.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: sparc64 pgalloc.h pgd_quicklist question
Date: Fri, 24 May 2002 09:05:26 -0700 (PDT) [thread overview]
Message-ID: <20020524.090526.105379973.davem@redhat.com> (raw)
In-Reply-To: <61DB42B180EAB34E9D28346C11535A783A775C@nocmail101.ma.tmpw.net>
From: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>
Date: Fri, 24 May 2002 11:12:25 -0500
Anyway, After looking at the SMP and UP configuration in pgalloc.h, could
you simply remove the UP/SMP differentiation in the routines, as in my
attachment? It looks to me, that the struct for pgt_quicklist is built
correctly for UP or SMP above this? I could be wrong on this....
That would waste 3/4 of every page allocated for PGDs.
We use the pointers to keep track of which bits of the page
are allocated to PGDs. So how about rewriting our code to
use bits in page->flags instead?
next parent reply other threads:[~2002-05-24 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61DB42B180EAB34E9D28346C11535A783A775C@nocmail101.ma.tmpw.net>
2002-05-24 16:05 ` David S. Miller [this message]
2002-05-24 16:28 ` sparc64 pgalloc.h pgd_quicklist question Russell King
2002-06-07 2:10 Holzrichter, Bruce
2002-06-07 8:18 ` Russell King
2002-06-09 22:36 ` Russell King
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=20020524.090526.105379973.davem@redhat.com \
--to=davem@redhat.com \
--cc=bruce.holzrichter@monster.com \
--cc=linux-kernel@vger.kernel.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