From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Introduce execlist_port_* accessors
Date: Tue, 31 Oct 2017 15:56:18 +0000 [thread overview]
Message-ID: <150946537832.23379.18065645226446687222@mail.alporthouse.com> (raw)
In-Reply-To: <150946451203.15081.4171110727087971223@mail.alporthouse.com>
Quoting Chris Wilson (2017-10-31 15:41:52)
> Quoting Mika Kuoppala (2017-10-31 15:27:33)
> > +static inline struct execlist_port *
> > +execlists_port_next(struct intel_engine_execlists * const execlists,
> > + const struct execlist_port * const port)
> > +{
> > + const unsigned int n = __port_add(port_index(port, execlists),
> > + 1,
> > + execlists->port_mask);
>
> How does this compare to
>
> if (port++ == execlists->port + execlists->port_mask)
> port = execlists->port;
>
> return port;
> ?
Rough estimate from bloat-o-meter
patch:
intel_lrc_irq_handler 1734 1926 +192
i915_guc_irq_handler 1522 1620 +98
execlists_cancel_port_requests 81 129 +48
intel_engine_dump 2030 2077 +47
intel_engine_init_cmd_parser 1132 1136 +4
capture 5633 5620 -13
delta:
i915_guc_irq_handler 1620 1617 -3
intel_lrc_irq_handler 1926 1790 -136
overall:
i915_guc_irq_handler 1522 1617 +95
intel_lrc_irq_handler 1734 1790 +56
execlists_cancel_port_requests 81 129 +48
intel_engine_dump 2030 2077 +47
intel_engine_init_cmd_parser 1132 1136 +4
capture 5633 5620 -13
But still +56 in irq_handler, that's mostly dequeue I guess. Can we do
better?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-31 15:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 15:27 [PATCH 1/2] drm/i915: Introduce execlist_port_* accessors Mika Kuoppala
2017-10-31 15:27 ` [PATCH 2/2] drm/i915: Move execlists port head instead of memmoving array Mika Kuoppala
2017-10-31 15:42 ` Chris Wilson
2017-11-02 15:07 ` Chris Wilson
2017-11-22 13:52 ` Mika Kuoppala
2017-11-22 13:57 ` Chris Wilson
2017-10-31 15:41 ` [PATCH 1/2] drm/i915: Introduce execlist_port_* accessors Chris Wilson
2017-10-31 15:56 ` Chris Wilson [this message]
2017-11-02 10:38 ` Mika Kuoppala
2017-11-02 10:57 ` Chris Wilson
2017-11-02 14:14 ` Mika Kuoppala
2017-11-02 14:15 ` Mika Kuoppala
2017-10-31 15:51 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " Patchwork
2017-11-02 14:32 ` [PATCH 1/2] " Mika Kuoppala
2017-11-02 15:03 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2017-11-30 9:10 [PATCH 0/2] execlist port handling improvements Mika Kuoppala
2017-11-30 9:10 ` [PATCH 1/2] drm/i915: Introduce execlist_port_* accessors Mika Kuoppala
2017-11-30 10:21 ` Chris Wilson
2017-10-19 14:39 Mika Kuoppala
2017-10-19 14:48 ` Chris Wilson
2017-10-20 12:00 ` Mika Kuoppala
2017-10-19 14:50 ` Chris Wilson
2017-10-20 10:34 ` Joonas Lahtinen
2017-10-20 11:12 ` Mika Kuoppala
2017-10-20 11:26 ` Chris Wilson
2017-10-20 12:53 ` Mika Kuoppala
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=150946537832.23379.18065645226446687222@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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.