From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915/gt: Apply the CSB w/a for all
Date: Mon, 17 Aug 2020 12:02:31 +0300 [thread overview]
Message-ID: <87d03p1w7s.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <159743629912.31882.4041606652398941372@build.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Chris Wilson (2020-08-14 20:41:32)
>> Quoting Mika Kuoppala (2020-08-14 19:41:14)
>> > Chris Wilson <chris@chris-wilson.co.uk> writes:
>> > > - entry = READ_ONCE(*csb);
>> > > - if (unlikely(entry == -1)) {
>> > > - preempt_disable();
>> > > - if (wait_for_atomic_us((entry = READ_ONCE(*csb)) != -1, 50))
>> >
>> > If we get this deep into desperation, should we start to apply more
>> > pressure. Ie, rmb instead of just instructing the compiler. And could also
>> > start to invalidate the entry which obviously if of no use.
>>
>> I had a rmb() here; removing it did not appear to make any difference
>> whatsoever to the average delay. The extreme case would be a full
>> mb(); clflush(); mb() read. I haven't timed the average for that....
>
> +static inline u64 __csb_read(u64 *csb)
> +{
> + mb();
> + clflush(csb);
> + mb();
> +
> + return READ_ONCE(*csb);
> +}
>
> [ 1554.274204] csb: 1793 misses, avg 475ns, max 14727ns
>
> So no better on average or at worst.
Well thanks for trying it out. We can attach it to hsdes as
a note that there is not much to be done on cpu side :O
-Mika
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-17 9:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 15:57 [Intel-gfx] [PATCH 1/3] drm/i915/gt: Widen CSB pointer to u64 for the parsers Chris Wilson
2020-08-14 15:57 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Wait for CSB entries on Tigerlake Chris Wilson
2020-08-14 15:57 ` Chris Wilson
2020-08-14 18:07 ` [Intel-gfx] " Chang, Bruce
2020-08-14 18:07 ` Chang, Bruce
2020-08-14 18:38 ` [Intel-gfx] " Chris Wilson
2020-08-14 18:38 ` Chris Wilson
2020-08-15 0:36 ` Chang, Bruce
2020-08-15 0:36 ` Chang, Bruce
2020-08-15 2:16 ` Chang, Bruce
2020-08-15 2:16 ` Chang, Bruce
2020-08-15 9:59 ` Chris Wilson
2020-08-15 9:59 ` Chris Wilson
2020-08-15 9:53 ` Chris Wilson
2020-08-15 9:53 ` Chris Wilson
2020-08-14 15:57 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Apply the CSB w/a for all Chris Wilson
2020-08-14 18:18 ` Chang, Bruce
2020-08-14 18:41 ` Mika Kuoppala
2020-08-14 19:41 ` Chris Wilson
2020-08-14 20:18 ` Chris Wilson
2020-08-17 9:02 ` Mika Kuoppala [this message]
2020-08-14 16:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/gt: Widen CSB pointer to u64 for the parsers Patchwork
2020-08-14 16:16 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-08-14 16:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-08-14 18:07 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-14 18:29 ` [Intel-gfx] [PATCH 1/3] " Mika Kuoppala
2020-08-14 19:43 ` Chris Wilson
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=87d03p1w7s.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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.