From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Update comment before i915_spin_request
Date: Fri, 5 Aug 2016 18:33:38 +0200 [thread overview]
Message-ID: <20160805163338.GF6232@phenom.ffwll.local> (raw)
In-Reply-To: <20160805163125.GG24508@nuc-i3427.alporthouse.com>
On Fri, Aug 05, 2016 at 05:31:25PM +0100, Chris Wilson wrote:
> On Fri, Aug 05, 2016 at 06:11:24PM +0200, Daniel Vetter wrote:
> > ~jiffie and a few usecs is 3 orders of magnitude different. A bit
> > much. This was changed in
> >
> > commit ca5b721e238226af1d767103ac852aeb8e4c0764
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Fri Dec 11 11:32:58 2015 +0000
> >
> > drm/i915: Limit the busy wait on requests to 5us not 10ms!
> >
> > But probably missed the comment since the change was non-local to the
> > comment.
>
> No, I was just using it as a pun referring to a jiffy being a small
> amount of time.
Too confusing in the context of the linux kernel ;-) Ack?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-05 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 16:11 [PATCH] drm/i915: Update comment before i915_spin_request Daniel Vetter
2016-08-05 16:31 ` Chris Wilson
2016-08-05 16:33 ` Daniel Vetter [this message]
2016-08-05 16:46 ` Chris Wilson
2016-08-06 5:29 ` ✗ Ro.CI.BAT: failure for " 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=20160805163338.GF6232@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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 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.