From: Keith Whitwell <keith@tungstengraphics.com>
To: Ian Romanick <idr@us.ibm.com>
Cc: Jon Smirl <jonsmirl@yahoo.com>,
lkml <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@linux.ie>,
"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: Re: DRM code reorganization
Date: Mon, 02 Aug 2004 19:27:32 +0100 [thread overview]
Message-ID: <410E8794.2030900@tungstengraphics.com> (raw)
In-Reply-To: <410E81C3.2070804@us.ibm.com>
>> ian: what about splitting the current memory management code into a
>> module that can be swapped for your new version?
>
>
> AFAIK, the only drivers that have any sort of in-kernel memory manager
> are the radeon (only used by the R200 driver) and i830. That memory
> manager only exists to support an NV_vertex_array_range-like extension
> that some Tungsten customers needed. I don't think there would be any
> benefit to making that swappable.
>
> Once the new memory manager is in, 80% (or more) of the code will be in
> user-mode anyway. The code that will be in the kernel should be generic
> enough to be completely sharable (i.e., in a generic DRM library).
Yes, the future is Ian's manager. The existing ones are built to be discarded
when something better comes along.
Keith
next prev parent reply other threads:[~2004-08-02 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 15:53 DRM code reorganization Jon Smirl
2004-08-02 18:02 ` Ian Romanick
2004-08-02 18:27 ` Keith Whitwell [this message]
2004-08-02 18:57 ` Dave Jones
2004-08-02 18:16 ` Alan Cox
2004-08-02 20:11 ` Ian Romanick
2004-08-02 20:42 ` Jon Smirl
2004-08-02 21:09 ` Dave Jones
2004-08-02 21:51 ` Michel Dänzer
2004-08-02 23:09 ` Jon Smirl
2004-08-02 23:24 ` Alan Cox
2004-08-02 20:45 ` Dave Jones
2004-08-02 23:53 ` Ian Romanick
2004-08-03 7:52 ` Keith Whitwell
2004-08-03 16:28 ` Ian Romanick
2004-08-03 16:49 ` Keith Whitwell
2004-08-03 0:06 ` Dave Airlie
2004-08-03 6:13 ` Eric Anholt
2004-08-02 23:48 ` Dave Airlie
2004-08-02 23:26 ` Alan Cox
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=410E8794.2030900@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.com \
--cc=jonsmirl@yahoo.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 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.