From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"Siluvery, Arun" <arun.siluvery@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
Matthias Dejaegher <matthias.dejaegher@intel.com>,
garry.lancaster@intel.com
Subject: Re: [RFC] libdrm_intel: Rework BO allocs to avoid rounding up to bucket size
Date: Fri, 29 Aug 2014 14:34:05 +0200 [thread overview]
Message-ID: <20140829123405.GC15520@phenom.ffwll.local> (raw)
In-Reply-To: <20140829111845.GF3557@nuc-i3427.alporthouse.com>
On Fri, Aug 29, 2014 at 12:18:45PM +0100, Chris Wilson wrote:
> What I've done in the past is kept a global pool of used pages to avoid
> clflushing fresh allocations in the kernel. That runs afoul of the ABI
> that we need to scrub new bo. With a create2 we could specify a pool to
> use that would be filp private and so have no greater information leak
> than the current reuse. Probably will still be frowned upon, but a fun
> idea to pursue...
I think a per-filp page cache would actually be fairly sane. Presuming the
added complexity can be justified with benchmarks ofc.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-08-29 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 10:02 [RFC] libdrm_intel: Optimize BO alloc to avoid rounding to bucket size Arun Siluvery
2014-08-29 10:02 ` [RFC] libdrm_intel: Rework BO allocs to avoid rounding up " Arun Siluvery
2014-08-29 10:16 ` Chris Wilson
2014-08-29 10:45 ` Siluvery, Arun
2014-08-29 11:18 ` Chris Wilson
2014-08-29 12:34 ` Daniel Vetter [this message]
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=20140829123405.GC15520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=arun.siluvery@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=garry.lancaster@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthias.dejaegher@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.