From: Christoph Hellwig <hch@infradead.org>
To: Mike Werner <werner@sgi.com>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [RFC/PATCH]Allow agp memory allocations to use node information
Date: Wed, 12 May 2004 21:26:15 +0100 [thread overview]
Message-ID: <20040512212615.A597@infradead.org> (raw)
In-Reply-To: <40A2714B.2F27EA35@sgi.com>; from werner@sgi.com on Wed, May 12, 2004 at 11:47:39AM -0700
not a lot of description here, he? :-)
On Wed, May 12, 2004 at 11:47:39AM -0700, Mike Werner wrote:
> diff -u linux-2.6.6.orig/drivers/char/agp/agp.h
> linux-2.6.6/drivers/char/agp/agp.h
> --- linux-2.6.6.orig/drivers/char/agp/agp.h Sun May 9 19:32:28 2004
>
> +++ linux-2.6.6/drivers/char/agp/agp.h Wed May 12 11:43:19 2004
> @@ -111,7 +111,7 @@
> int (*remove_memory)(struct agp_memory *, off_t, int);
> struct agp_memory *(*alloc_by_type) (size_t, int);
> void (*free_by_type)(struct agp_memory *);
> - void *(*agp_alloc_page)(void);
> + void *(*agp_alloc_page)(int);
> void (*agp_destroy_page)(void *);
Wrong interface. We need to pass a struct agp_bridge_data to
each of the methods anyway for proper support for multiple AGP
bridges in a single system. And once you have that you can simply
use the node id your patches stores in agp_bridge_data.
> +++ linux-2.6.6/drivers/char/agp/intel-mch-agp.c Wed May 12
> 11:16:02 2004
> @@ -43,7 +43,7 @@
> if (pg_count != 1)
> return NULL;
>
> - addr = agp_bridge->driver->agp_alloc_page();
> + addr = agp_bridge->driver->agp_alloc_page(AGPGART_DEFAULT_NODE);
wrong default again. for the agp bridges that have an associated pci
device (aka about everything except hpzx and alpha IIRC) you should
use pcibus_to_cpumask (or what the thing was called). For the others
you should try to contact the maintainers for a proper choice.
prev parent reply other threads:[~2004-05-12 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 18:47 Mike Werner
2004-05-12 20:26 ` Christoph Hellwig [this message]
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=20040512212615.A597@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@sgi.com \
/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
all inboxes | Powered by JetHome®