public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] lib/i915/perf: break generated code in separate files
Date: Tue, 10 Mar 2020 18:31:59 +0200	[thread overview]
Message-ID: <ccdedb7a-1a41-0358-d76c-844a6827b9f8@intel.com> (raw)
In-Reply-To: <20200310162946.2335031-2-lionel.g.landwerlin@intel.com>

On 10/03/2020 18:29, Lionel Landwerlin wrote:
> Initially all the generated code was per generation. Eventually we
> grouped it into a single file to reuse as much as possible equation
> code (this reduce binary size by a factor). So many equations are just
> the same from generation to generation.
>
> But this generated file is 200k lines long...
>
> This change puts all the metrics into a single file and then breaks
> down the metric sets per generation.


I meant equations into a single file and then ....


-Lionel


>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-03-10 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 16:29 [igt-dev] [PATCH i-g-t 1/2] lib/i915/perf: remove generation code for mathml render Lionel Landwerlin
2020-03-10 16:29 ` [igt-dev] [PATCH i-g-t 2/2] lib/i915/perf: break generated code in separate files Lionel Landwerlin
2020-03-10 16:31   ` Lionel Landwerlin [this message]
2020-03-10 16:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] lib/i915/perf: remove generation code for mathml render Patchwork
2020-03-10 17:00 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-10 21:53 ` [igt-dev] ✓ Fi.CI.IGT: " 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=ccdedb7a-1a41-0358-d76c-844a6827b9f8@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox