From: Christopher Wedgwood <cw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.x bk) efi_memmap_walk_uc
Date: Tue, 29 Jul 2003 19:03:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105950566703962@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105883467032028@msgid-missing>
On Tue, Jul 29, 2003 at 11:45:40AM -0700, Luck, Tony wrote:
> Even though you are the only user ... it would seem prudent
> to define some generic interface.
I agree but I'm more inclined to think that should be part of an EFI
interfaces cleanup though and more medium to long term perhaps? I'd
rather see a small limited interface initially and then have that
'fixed' as requirements become more obvious.
> 2) There is no way for another non-kernel user of uncacheable
> memory to share the resource with you.
The current fetchop driver export interfaces:
/*-----------------------------------------------------------------------------
* KERNEL APIs
* Note: right now, these APIs return a full page of fetchops. If these
* interfaces are used often for tasks which do not require a full page of
* fetchops, new APIs should be added to suballocate out of a single page.
*/
unsigned long
fetchop_kalloc_page(int nid)
{
if (fetchop_update_stats(1, 1) < 0)
return 0;
return fetchop_alloc_page(nid);
}
EXPORT_SYMBOL(fetchop_kalloc_page);
void
fetchop_kfree_page(unsigned long maddr)
{
fetchop_free_page(maddr);
fetchop_update_stats(-1, -1);
}
EXPORT_SYMBOL(fetchop_kfree_page);
Might these be more generically useful at some later stage?
Thanks,
--cw
next prev parent reply other threads:[~2003-07-29 19:03 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 [this message]
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
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-105950566703962@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.