From: Thomas Hellstrom <thellstrom@vmware.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm: enable render-nodes by default
Date: Thu, 20 Mar 2014 15:59:17 +0100 [thread overview]
Message-ID: <532B0245.7050504@vmware.com> (raw)
In-Reply-To: <20140320143600.GA2020@gmail.com>
On 03/20/2014 03:36 PM, Jerome Glisse wrote:
>
> In any case this is not a render node issue and there is no reasons to force
> full VRAM eviction or anything like that.
This comment suggests you haven't read the discussion fully.
VRAM eviction was discussed in the context of legacy nodes.
This is a render node issue because with legacy nodes you can work
around insufficient command checking.
With render nodes you can't.
/Thomas
> Cheers,
> Jérôme
next prev parent reply other threads:[~2014-03-20 14:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 13:43 [PATCH] drm: enable render-nodes by default David Herrmann
2014-03-16 13:43 ` David Herrmann
2014-03-17 10:07 ` Daniel Vetter
2014-03-17 10:07 ` Daniel Vetter
2014-03-17 16:43 ` [PATCH v2] " David Herrmann
2014-03-20 6:43 ` Thomas Hellstrom
2014-03-20 7:36 ` David Herrmann
2014-03-20 8:48 ` Thomas Hellstrom
2014-03-20 9:05 ` David Herrmann
2014-03-20 9:27 ` Thomas Hellstrom
2014-03-20 9:43 ` David Herrmann
2014-03-20 10:28 ` Thomas Hellstrom
2014-03-20 14:36 ` Jerome Glisse
2014-03-20 14:44 ` Ilia Mirkin
2014-03-20 15:35 ` Jerome Glisse
2014-03-20 17:39 ` Ilia Mirkin
2014-03-20 14:59 ` Thomas Hellstrom [this message]
2014-03-20 15:34 ` Jerome Glisse
2014-03-20 15:49 ` Thomas Hellstrom
2014-03-20 17:04 ` Jerome Glisse
2014-03-20 17:34 ` Rob Clark
2014-03-20 20:54 ` Thomas Hellstrom
2014-03-20 21:13 ` Rob Clark
2014-03-21 7:10 ` Daniel Vetter
2014-03-21 8:29 ` Thomas Hellstrom
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=532B0245.7050504@vmware.com \
--to=thellstrom@vmware.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.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.