From: Dave Airlie <airlied@gmail.com>
To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: sync_file rcu adoption and semaphore changes.
Date: Wed, 15 Mar 2017 14:27:45 +1000 [thread overview]
Message-ID: <20170315042749.13259-1-airlied@gmail.com> (raw)
Okay I've listened and people said this should use rcu, so I've
tried to work out what that looks like, and I present my first pass
at using rcu for sync_file. I'm pretty sure I've probably missed some
fundamental things here.
As to Chris's reserveration_object questions, yes it does the rcu stuff
and I suppose it does the exclusive fence (with 0 shared fences), so
we'd want to make sync_file wrap reservation objects, not semaphores,
since the main reason I'm at sync files in the first place is the file
part for sharing them between processes.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-15 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 4:27 Dave Airlie [this message]
2017-03-15 4:27 ` [PATCH 1/4] sync_file: add a mutex to protect fence and callback members. (v22) Dave Airlie
2017-03-15 4:27 ` [PATCH 2/4] sync_file: add replace and export some functionality (v2) Dave Airlie
2017-03-15 4:27 ` [PATCH 3/4] amdgpu/cs: split out fence dependency checking Dave Airlie
[not found] ` <20170315042749.13259-1-airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-15 4:27 ` [PATCH 4/4] amdgpu: use sync file for shared semaphores Dave Airlie
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=20170315042749.13259-1-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=amd-gfx@lists.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 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.