From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Luca Coelho <luciano.coelho@intel.com>, intel-gfx@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] [PATCH v2 2/3] drm/i915: add a dedicated workqueue inside drm_i915_private
Date: Wed, 24 May 2023 12:05:30 +0100 [thread overview]
Message-ID: <2128eea5-32f7-dbed-6c56-162038883dc3@linux.intel.com> (raw)
In-Reply-To: <0a1cf2a3-3402-04dd-b276-4d1ecd0d170b@linux.intel.com>
On 24/05/2023 12:00, Tvrtko Ursulin wrote:
>
> On 24/05/2023 10:05, Luca Coelho wrote:
8<
>> if (pool_free_older_than(pool, HZ))
>> - schedule_delayed_work(&pool->work,
>> - round_jiffies_up_relative(HZ));
>> + queue_delayed_work(gt->i915->unordered_wq, &pool->work,
>> + round_jiffies_up_relative(HZ));
>> }
>> static void pool_retire(struct i915_active *ref)
>> @@ -99,6 +100,7 @@ static void pool_retire(struct i915_active *ref)
>> struct intel_gt_buffer_pool_node *node =
>> container_of(ref, typeof(*node), active);
>> struct intel_gt_buffer_pool *pool = node->pool;
>> + struct intel_gt *gt = container_of(pool, struct intel_gt,
>> buffer_pool);
>
> ... although I am beginning to wonder if intel_gt_buffer_pool shouldn't
> just gain a gt backpointer? That would decouple things more instead of
> tying the implementation with intel_gt implicitly. Not a strong
> direction though.
Never mind on this point, code already assumes this relationships for
instance in node_create().
Regards,
Tvrtko
next prev parent reply other threads:[~2023-05-24 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:05 [Intel-gfx] [PATCH v2 0/3] drm/i915: implement internal workqueues Luca Coelho
2023-05-24 9:05 ` [Intel-gfx] [PATCH v2 1/3] drm/i915: use pointer to i915 instead of rpm in wakeref Luca Coelho
2023-05-24 10:42 ` Tvrtko Ursulin
2023-05-26 10:43 ` Jani Nikula
2023-05-24 9:05 ` [Intel-gfx] [PATCH v2 2/3] drm/i915: add a dedicated workqueue inside drm_i915_private Luca Coelho
2023-05-24 11:00 ` Tvrtko Ursulin
2023-05-24 11:05 ` Tvrtko Ursulin [this message]
2023-05-24 12:25 ` Coelho, Luciano
2023-05-26 11:30 ` Jani Nikula
2023-05-28 14:58 ` Coelho, Luciano
2023-05-24 9:05 ` [Intel-gfx] [PATCH v2 3/3] drm/i915/selftests: add local workqueue for SW fence selftest Luca Coelho
2023-05-24 11:01 ` Tvrtko Ursulin
2023-05-24 11:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: implement internal workqueues (rev2) Patchwork
2023-05-24 11:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-05-24 11:18 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=2128eea5-32f7-dbed-6c56-162038883dc3@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luciano.coelho@intel.com \
--cc=rodrigo.vivi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox