From: Daniel Vetter <daniel@ffwll.ch>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Lucas Stach <dev@lynxeye.de>, r6144 <rainy6144@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: GEM-related desktop sluggishness due to linear-time arch_get_unmapped_area_topdown()
Date: Tue, 29 Mar 2011 22:26:08 +0200 [thread overview]
Message-ID: <20110329202608.GA3454@viiv.ffwll.ch> (raw)
In-Reply-To: <AANLkTin_v5h==E0i5mQgK2AEdaZhwViykr3acbz4CW0k@mail.gmail.com>
On Tue, Mar 29, 2011 at 03:45:34PM -0400, Jerome Glisse wrote:
> Short lived & small bo would definitly doesn't work well for this kind
> of API, it would all be a function of the ioctl cost. But i am not
> sure the drawback would be that big, intel tested with pread/pwrite
> and gived up don't remember why. For the vbo case you describe the
> scheme i was thinking would be : allocate bo and on buffer data call
> upload to the allocated bo using the bind user page feature that would
> mean zero extra copy operation. For the fire forget case of vbo,
> likely somekind of transient buffer would be more appropriate.
Just to clarify: Uploads to linear buffers are all done with pwrite (due
to an api foobar, it's not so great for 2d/tiled stuff). It's amazing how
much faster that is: Switching vbo's from mmpa to pwrite has given a few
percent more fps in openarena in i915g! As long as the chunk you're gonna
write fits into L1 cache, it's probably a net win.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-03-29 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 11:16 GEM-related desktop sluggishness due to linear-time arch_get_unmapped_area_topdown() r6144
2011-03-28 18:13 ` Lucas Stach
2011-03-29 14:22 ` Jerome Glisse
2011-03-29 14:44 ` r6144
2011-03-29 15:23 ` Jerome Glisse
2011-03-29 18:01 ` Lucas Stach
2011-03-29 19:45 ` Jerome Glisse
2011-03-29 20:26 ` Daniel Vetter [this message]
2011-03-29 21:04 ` Jerome Glisse
2011-03-29 21:57 ` Dave Airlie
2011-03-30 7:32 ` Chris Wilson
2011-03-30 13:28 ` Jerome Glisse
2011-03-30 14:07 ` Chris Wilson
2011-03-30 15:07 ` Jerome Glisse
2011-03-30 15:22 ` Chris Wilson
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=20110329202608.GA3454@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--cc=dev@lynxeye.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rainy6144@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox