All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/5] drm/nouveau: add reservation to nouveau_gem_ioctl_cpu_prep
Date: Tue, 21 Jan 2014 16:29:22 +0100	[thread overview]
Message-ID: <52DE9252.6050007@canonical.com> (raw)
In-Reply-To: <52DE8F98.3020305@vmware.com>

Hey,

op 21-01-14 16:17, Thomas Hellstrom schreef:
> Maarten, for this and the other patches in this series,
>
> I seem to recall we have this discussion before?
> IIRC I stated that reservation was a too heavy-weight lock to hold to
> determine whether a buffer was idle? It's a pretty nasty thing to build in.
>
I've sent this patch after determining that this already didn't end up being heavyweight.
Most places were already using the fence_lock and reservation, I just fixed up the few
places that didn't hold a reservation while waiting. Converting the few places that didn't
ended up being trivial, so I thought I'd submit it.

If a tryreserve fails it's a good indication that the buffer is NOT idle, no need to check the
fences too in that case.

I ended up converting this so I could use shared/exclusive fence slots internally in nouveau,
allowing multiple readers to access the buffers in parallel. See commit
"drm/nouveau: first stab at using shared fences for readable objects" at
http://cgit.freedesktop.org/~mlankhorst/linux/log/

But doing this required killing fence_lock.

~Maarten

  reply	other threads:[~2014-01-21 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 13:04 [PATCH 1/5] drm/ttm: kill off some members to ttm_validate_buffer Maarten Lankhorst
2014-01-21 13:04 ` [PATCH 2/5] drm/nouveau: add reservation to nouveau_gem_ioctl_cpu_prep Maarten Lankhorst
2014-01-21 15:17   ` Thomas Hellstrom
2014-01-21 15:29     ` Maarten Lankhorst [this message]
2014-01-21 17:44       ` Thomas Hellstrom
2014-01-22  8:19         ` Maarten Lankhorst
2014-01-22  9:40           ` Thomas Hellstrom
2014-01-22  9:55             ` Maarten Lankhorst
2014-01-22 10:27               ` Thomas Hellstrom
2014-01-22 10:58                 ` Maarten Lankhorst
2014-01-22 12:11                   ` Thomas Hellstrom
2014-01-22 12:38                     ` Maarten Lankhorst
2014-01-22 12:52                       ` Thomas Hellstrom
2014-01-22 15:09                         ` Daniel Vetter
2014-01-22 15:30                           ` Thomas Hellstrom
2014-01-22 15:41                           ` Thomas Hellstrom
2014-01-22 12:43                     ` Maarten Lankhorst
2014-01-21 13:04 ` [PATCH 3/5] drm/nouveau: require reservations for nouveau_fence_sync and nouveau_bo_fence Maarten Lankhorst
2014-01-21 13:04 ` [PATCH 4/5] drm/ttm: call ttm_bo_wait while inside a reservation Maarten Lankhorst
2014-01-21 13:04 ` [PATCH 5/5] drm/ttm: kill fence_lock Maarten Lankhorst
2014-01-21 14:40   ` [PATCH v2] " Maarten Lankhorst

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=52DE9252.6050007@canonical.com \
    --to=maarten.lankhorst@canonical.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.