From: Thomas Hellstrom <thomas@shipmail.org>
To: Dave Airlie <airlied@gmail.com>
Cc: airlied@redhat.com, Thomas Hellstrom <thellstrom@vmware.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/ttm: Optimize delayed buffer destruction
Date: Tue, 19 Oct 2010 09:21:24 +0200 [thread overview]
Message-ID: <4CBD46F4.7080505@shipmail.org> (raw)
In-Reply-To: <AANLkTikg2CFd02AHSahEddZG8=BC=a8WWQ2GM2nxY3Qw@mail.gmail.com>
On 10/19/2010 05:57 AM, Dave Airlie wrote:
> On Thu, Oct 14, 2010 at 3:18 AM, Thomas Hellstrom<thellstrom@vmware.com> wrote:
>
>> This commit replaces the ttm_bo_cleanup_ref function with two new functions.
>> One for the case where the bo is not yet on the delayed destroy list, and
>> one for the case where the bo was on the delayed destroy list, at least at
>> the time of call. This makes it possible to optimize the two cases somewhat.
>>
> I tried booting this today, but on radeon starting X hit a recursive
> spin lock on the lru lock.
>
> (annotated below)
>
>
New patches sent.
/Thomas
next prev parent reply other threads:[~2010-10-19 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 17:17 [PATCH 0/0] ttm patches for drm-next Thomas Hellstrom
2010-10-13 17:17 ` [PATCH 1/2] drm/ttm: Avoid using the ttm_mem_type_manager::put_locked function Thomas Hellstrom
2010-10-13 17:18 ` [PATCH 2/2] drm/ttm: Optimize delayed buffer destruction Thomas Hellstrom
2010-10-19 3:57 ` Dave Airlie
2010-10-19 7:21 ` Thomas Hellstrom [this message]
2010-10-19 4:11 ` [PATCH 1/2] drm/ttm: Avoid using the ttm_mem_type_manager::put_locked function Dave Airlie
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 7:00 [PATCH 0/2] ttm patches for drm-next v2 Thomas Hellstrom
2010-10-19 7:01 ` [PATCH 1/2] drm/ttm: Avoid using the ttm_mem_type_manager::put_locked function Thomas Hellstrom
2010-10-19 7:01 ` [PATCH 2/2] drm/ttm: Optimize delayed buffer destruction Thomas Hellstrom
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=4CBD46F4.7080505@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@vmware.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.