From: Jon Smirl <jonsmirl@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
Dave Airlie <airlied@linux.ie>
Subject: Reusing the slab allocator
Date: Wed, 10 Aug 2005 12:28:49 -0400 [thread overview]
Message-ID: <9e473391050810092835b3ef27@mail.gmail.com> (raw)
We need a memory manager for the VRAM on video cards. The most common
video cards have been 2MB and 512MB memory. Is it possible to reuse
the kernel slab allocator for managing this memory?
There are a couple of other odd constraints.
1) Some objects need to be allocated on boundaries, like 64B or even
1KB divisible addresses.
2) It would be best if the allocation bookkeeping data structures were
kept in system RAM. It may not be simple to access VRAM for read/write
of bookkeeping info. VRAM can require slow PCI cycles or need high
mem mappings to access.
If possible I'd rather reuse an existing manager than write a new one.
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2005-08-10 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:28 Jon Smirl [this message]
2005-08-13 16:17 ` Reusing the slab allocator Pekka Enberg
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=9e473391050810092835b3ef27@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@linux.ie \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox