From: "Michel Dänzer" <michel@daenzer.net>
To: Tejun Heo <tj@kernel.org>,
Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue
Date: Mon, 4 Jul 2016 12:58:32 +0900 [thread overview]
Message-ID: <9e69b1fd-eb93-1fee-15af-c905ee3a202f@daenzer.net> (raw)
In-Reply-To: <20160702134614.GB17431@htj.duckdns.org>
On 02.07.2016 22:46, Tejun Heo wrote:
> On Sat, Jul 02, 2016 at 04:33:50PM +0530, Bhaktipriya Shridhar wrote:
>> alloc_workqueue replaces deprecated create_singlethread_workqueue().
>>
>> A dedicated workqueue has been used since work items need to be flushed
>> as a group rather than individually.
>>
>> Since the flip_queue workqueue is involved in page-flipping and is not
>> being used on a memory reclaim path, WQ_MEM_RECLAIM has not been set.
>>
>> Since there are only a fixed number of work items, explicit concurrency
>> limit is unnecessary here.
>
> What are the involved work items?
drivers/gpu/drm/radeon/radeon_display.c:radeon_flip_work_func()
> Is it safe to run them concurrently?
Concurrently with what exactly?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2016-07-04 3:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 11:03 Bhaktipriya Shridhar
2016-07-02 13:46 ` Tejun Heo
2016-07-04 3:58 ` Michel Dänzer [this message]
2016-07-05 21:06 ` Tejun Heo
2016-07-06 3:12 ` Michel Dänzer
2016-07-06 13:45 ` Tejun Heo
2016-07-07 3:32 ` Michel Dänzer
2016-07-07 7:43 ` Christian König
2016-07-08 5:52 ` Michel Dänzer
2016-07-12 17:52 ` Tejun Heo
2016-07-16 11:30 ` [PATCH v2] " Bhaktipriya Shridhar
2016-07-18 13:21 ` Christian König
2016-07-19 0:48 ` Tejun Heo
2016-07-28 16:14 ` Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2016-06-28 17:26 [PATCH] " Bhaktipriya Shridhar
2016-06-28 17:44 ` Bhaktipriya Shridhar
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=9e69b1fd-eb93-1fee-15af-c905ee3a202f@daenzer.net \
--to=michel@daenzer.net \
--cc=alexander.deucher@amd.com \
--cc=bhaktipriya96@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®