public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Uncached memory allocator for ia64.
Date: Tue, 14 Sep 2004 15:16:29 +0000	[thread overview]
Message-ID: <20040914151629.GA21118@lnx-holt.americas.sgi.com> (raw)

In an effort to get the SGI Special Memory driver into the kernel,
Christoph Hellwig pointed me at a discussion of a general purpose uncached
memory allocator.  The thread is here:

http://www.gelato.unsw.edu.au/linux-ia64/0307/6218.html

I would like to reopen this discussion to determine the scope of work
that would need to be done.

I would like to start with the general, what are we trying to solve?
I can not think of a single reason aside from the previously discussed
min state area for the kernel to ever need to work with memory uncached.

Assuming there is no reason, can we pare this discussion back to a page
based allocator?  That would be much simpler to work with and would not
need to recombine fragments.

Given a page based allocator, can we just use the code that is in the
fetchop driver?  It does a per-node page based allocation.  Can that
code be renamed to no longer mention mspec?  Where in the tree should
this functionality live?  Would it be acceptable to always work with
physical addresses?

Thanks,
Robin Holt


             reply	other threads:[~2004-09-14 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 15:16 Robin Holt [this message]
2004-09-15  8:23 ` Uncached memory allocator for ia64 David Mosberger
2004-09-15 11:04 ` Robin Holt
2004-09-15 11:14 ` David Mosberger
2004-09-17 14:34 ` Robin Holt
2004-09-23 21:09 ` Robin Holt
2004-09-23 22:12 ` Luck, Tony
2004-09-23 23:01 ` Robin Holt
2004-09-25 12:40 ` Robin Holt
2004-09-29 14:24 ` David Mosberger
2004-09-29 15:43 ` Robin Holt
2004-09-29 16:02 ` David Mosberger

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=20040914151629.GA21118@lnx-holt.americas.sgi.com \
    --to=holt@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