From: Christopher Wedgwood <cw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.x bk) efi_memmap_walk_uc
Date: Wed, 30 Jul 2003 00:00:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105952331923555@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105883467032028@msgid-missing>
On Tue, Jul 29, 2003 at 03:47:34PM -0700, Luck, Tony wrote:
> min_state areas for MCA will be smaller than a page ... so *my* use
> of this allocator doesn't require multi-page.
I'm guessing you'll only need 1k or 4k per-cpu right? What about any
padding here?
On Tue, Jul 29, 2003 at 03:54:27PM -0700, David Mosberger wrote:
> Let's stick with a tried-and-true malloc/free-like interface (nobody
> every gets size arguments to free() right, do they?).
I'd like to claim this is too complex and that page would suffice
except clearly for MINSTATE purposes page granularity is wasteful.
Jack also pointed out for MINSTATE handling on SN2 we would want
local-node pages so perhaps something like:
u64 ia64_uc_alloc(u64 nbytes, int nodeid, int flags);
void ia64_uc)free(u64 paddr);
Simply claim '0' is not a useful physical address in this sense and
thus signifies and error?
The 'flags' seems overly complex but would be a mechanism to insist
that memory is allocated from the given node (as opposed to just a
hint for locality).
Comments?
--cw
next prev parent reply other threads:[~2003-07-30 0:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 0:43 [PATCH] (2.4.x bk) efi_memmap_walk_uc Christopher Wedgwood
2003-07-22 2:16 ` Bjorn Helgaas
2003-07-22 2:58 ` Christopher Wedgwood
2003-07-22 3:08 ` Bjorn Helgaas
2003-07-22 4:43 ` Christopher Wedgwood
2003-07-25 1:15 ` David Mosberger
2003-07-29 18:34 ` Christopher Wedgwood
2003-07-29 18:45 ` Luck, Tony
2003-07-29 19:03 ` Christopher Wedgwood
2003-07-29 20:41 ` David Mosberger
2003-07-29 21:15 ` Christopher Wedgwood
2003-07-29 21:31 ` David Mosberger
2003-07-29 21:34 ` Luck, Tony
2003-07-29 22:05 ` Jack Steiner
2003-07-29 22:07 ` Christopher Wedgwood
2003-07-29 22:26 ` Luck, Tony
2003-07-29 22:30 ` David Mosberger
2003-07-29 22:35 ` Christopher Wedgwood
2003-07-29 22:37 ` Christopher Wedgwood
2003-07-29 22:47 ` Luck, Tony
2003-07-29 22:48 ` David Mosberger
2003-07-29 22:54 ` David Mosberger
2003-07-29 23:49 ` Jack Steiner
2003-07-29 23:54 ` Christopher Wedgwood
2003-07-29 23:56 ` Jack Steiner
2003-07-30 0:00 ` Christopher Wedgwood [this message]
2003-07-30 0:02 ` Christopher Wedgwood
2003-07-30 0:05 ` David Mosberger
2003-07-30 0:12 ` David Mosberger
2003-07-30 0:22 ` Jack Steiner
2003-07-30 9:21 ` Christoph Hellwig
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=marc-linux-ia64-105952331923555@msgid-missing \
--to=cw@sgi.com \
--cc=linux-ia64@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