All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915/skl: Split the SKL PCI ids by GT
Date: Fri, 30 Jan 2015 17:25:31 +0100	[thread overview]
Message-ID: <20150130162531.GG14009@phenom.ffwll.local> (raw)
In-Reply-To: <20150129201113.GM12268@jeffdesk>

On Thu, Jan 29, 2015 at 02:11:13PM -0600, Jeff McGee wrote:
> On Thu, Jan 29, 2015 at 02:13:38PM +0000, Damien Lespiau wrote:
> > We need to have a separate GT3 struct intel_device_info to declare they
> > have a second VCS. Let's start by splitting the PCI ids per-GT.
> > 
> Would it be a good idea to do more programmatic population of
> these fields, rather than creating an entire new instance of the
> struct just to alter one field? This relates to our other
> conversation about the memory consumed by the 30+ device infos
> and the concern when adding new fields.

Broken record maintainer blurb:

Please provide hard data when justifying memory savings in the kmd. I see
a lot of people throwing around ideas and it seems a general concern, but
like with everything else we need to strike a cost/benefit balance and opt
for the most efficient way to save these bytes.

Which usually means shrinking down one of the runtime structs we allocate
by the thousands.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-01-30 16:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 14:13 [PATCH 1/3] drm/i915/skl: Split the SKL PCI ids by GT Damien Lespiau
2015-01-29 14:13 ` [PATCH 2/3] drm/i915/skl: Declare that GT3 has a second VCS Damien Lespiau
2015-02-04  1:55   ` Rodrigo Vivi
2015-02-04  9:27     ` Daniel Vetter
2015-02-04 13:22       ` [PATCH 2/3 v2] " Damien Lespiau
2015-02-04 15:43         ` Rodrigo Vivi
2015-01-29 14:13 ` [PATCH 3/3] drm/i915/skl: Remove the check enforcing VCS2 to be gen8 only Damien Lespiau
2015-01-31 17:17   ` shuang.he
2015-02-04  1:55   ` Rodrigo Vivi
2015-02-04  9:28     ` Daniel Vetter
2015-01-29 20:11 ` [PATCH 1/3] drm/i915/skl: Split the SKL PCI ids by GT Jeff McGee
2015-01-30  7:30   ` Jani Nikula
2015-01-30 16:05     ` Jeff McGee
2015-02-02 12:01     ` Damien Lespiau
2015-01-30 16:25   ` Daniel Vetter [this message]
2015-02-04  1:51 ` Rodrigo Vivi
2015-02-04 11:58   ` Damien Lespiau
2015-02-04 13:10   ` Damien Lespiau
2015-02-04 15:41     ` Rodrigo Vivi

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=20150130162531.GG14009@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=damien.lespiau@intel.com \
    --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.