From: Luca Barbieri <luca.barbieri@gmail.com>
To: Pauli Nieminen <suokkos@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
dri-devel@lists.sourceforge.net,
"Jerome Glisse" <jglisse@redhat.com>
Subject: Re: [RFC] drm/ttm: add pool wc/uc page allocator
Date: Wed, 3 Mar 2010 13:47:43 +0100 [thread overview]
Message-ID: <ff13bc9a1003030447x24e8c9caw10a4a6d39078cf09@mail.gmail.com> (raw)
In-Reply-To: <548cdfc21003030413h9594bb1hb543d998844fdd1e@mail.gmail.com>
While this is almost surely a good idea, note that userspace caching
and suballocation substantially improves Mesa performance even on PCIe
systems.
This is mostly due to the unavoidable overhead of kernel calls and
pagetable modifications, as well as the avoidable linear search the
kernel currently does to find an empty space in virtual address space,
as well as the additional pagefaults.
Userspace caching and suballocation mean that you just have to compute
a pointer, which you cannot beat with any kernel-space solution. This
is also the way glibc allocates normal memory with malloc(), for the
same reason.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-03 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 21:30 [RFC] drm/ttm: add pool wc/uc page allocator Pauli Nieminen
2010-03-01 22:32 ` Pauli Nieminen
2010-03-02 10:56 ` Michel Dänzer
[not found] ` <4B8CFB1B.1020806@shipmail.org>
2010-03-03 12:13 ` Pauli Nieminen
2010-03-03 12:47 ` Luca Barbieri [this message]
2010-03-03 13:23 ` Thomas Hellstrom
2010-03-03 14:03 ` Luca Barbieri
2010-03-03 14:19 ` Thomas Hellstrom
2010-03-03 13:33 ` Jerome Glisse
2010-03-03 14:23 ` Pauli Nieminen
2010-03-03 14:50 ` Jerome Glisse
2010-03-03 15:46 ` Pauli Nieminen
2010-03-03 16:02 ` Jerome Glisse
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=ff13bc9a1003030447x24e8c9caw10a4a6d39078cf09@mail.gmail.com \
--to=luca.barbieri@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jglisse@redhat.com \
--cc=michel@daenzer.net \
--cc=suokkos@gmail.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 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.