From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 37142] Too much vertex buffers uploads
Date: Thu, 12 May 2011 13:27:11 -0700 (PDT)
Message-ID: <20110512202712.19FC713004F@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 44E2D9E759
for ;
Thu, 12 May 2011 13:27:12 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=37142
--- Comment #4 from Pierre-Eric Pelloux-Prayer 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.