From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37142] Too much vertex buffers uploads
Date: Thu, 12 May 2011 13:27:11 -0700 (PDT) [thread overview]
Message-ID: <20110512202712.19FC713004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37142-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37142
--- Comment #4 from Pierre-Eric Pelloux-Prayer <pelloux@gmail.com> 2011-05-12 13:27:09 PDT ---
(In reply to comment #2)
> (In reply to comment #0)
> > What do you think ?
>
> You can't optimize the uploads because the sizes of all buffers are not known
> when glLockArraysEXT is called. The only things you've got are pointers to the
> buffers.
Sure, but I was thinking to something more like :
- glLockArraysEXT does nothing more than curently
- uploading a vertex buffer is done as before except in one case : when trying
to upload the same buffer AND glLock is enabled => the uploading is skipped as
data is already in GPU memory (which is the case shown in the attached trace
file)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-12 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 15:11 [Bug 37142] New: Too much vertex buffers uploads bugzilla-daemon
2011-05-12 15:15 ` [Bug 37142] " bugzilla-daemon
2011-05-12 17:54 ` bugzilla-daemon
2011-05-12 17:55 ` bugzilla-daemon
2011-05-12 19:55 ` bugzilla-daemon
2011-05-12 20:19 ` bugzilla-daemon
2011-05-12 20:27 ` bugzilla-daemon [this message]
2011-05-13 7:11 ` bugzilla-daemon
2011-05-13 16:22 ` bugzilla-daemon
2011-05-17 12:33 ` bugzilla-daemon
2014-04-13 11:20 ` bugzilla-daemon
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=20110512202712.19FC713004F@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).