All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anuj Phogat <anuj.phogat@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel@ffwll.ch>,
	Anuj Phogat <anuj.phogat@gmail.com>,
	intel-gfx@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH v2 1/2] i965/gen9: Pass alignment as function parameter in drm_intel_gem_bo_alloc_internal()
Date: Tue, 23 Jun 2015 16:44:52 -0700	[thread overview]
Message-ID: <CAP5d04HX1To_GbdoibyVErD-4D7t-Wgy1Ee_Q=k-64FcU4cMVw@mail.gmail.com> (raw)
In-Reply-To: <20150622200441.GI31353@nuc-i3427.alporthouse.com>

On Mon, Jun 22, 2015 at 1:04 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Mon, Jun 22, 2015 at 09:51:08PM +0200, Daniel Vetter wrote:
>> On Mon, Jun 22, 2015 at 11:47:02AM -0700, Anuj Phogat wrote:
>> > and use it to initialize the align variable in drm_intel_bo.
>> >
>> > In case of YF/YS tiled buffers libdrm need not know about the tiling
>> > format because these buffers don't have hardware support to be tiled
>> > or detiled through a fenced region. But, libdrm still need to know
>> > about buffer alignment restrictions because kernel uses it when
>> > resolving the relocation.
>> >
>> > Mesa uses drm_intel_gem_bo_alloc_for_render() to allocate Yf/Ys buffers.
>> > So, use the passed alignment value in this function. Note that we continue
>> > ignoring the alignment value passed to drm_intel_gem_bo_alloc() to follow
>> > the previous behavior.
>> >
>> > V2: Add a condition to avoid allocation from cache. (Ben)
>>
>> This will hurt badly since some programs love to cycle through textures.
>> You can still allocate from the cache, you only need to update the
>> alignement constraint. The kernel will move the buffer on the next execbuf
>> if it's misplaced.
>
> For llc, using fresh pages just puts memory and aperture pressure (plus
> a small amount of interface pressure) on the system by allocating more bo.
>
> For !llc, it is far better to move an object in the GTT to match a
> change in alignment than it is to allocate fresh pages (and deallocate
> stale pages).
Could you please explain this and point me to what you want to be
changed in this patch?

> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-23 23:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11  0:20 [PATCH 1/2] i965/gen9: Pass alignment as function parameter in drm_intel_gem_bo_alloc_internal() Anuj Phogat
2015-04-11  0:20 ` [PATCH 2/2] Set alignment value in drm_intel_add_validate_buffer() Anuj Phogat
2015-05-20 21:01   ` Anuj Phogat
2015-06-09 22:00     ` Anuj Phogat
2015-06-19 22:52   ` Anuj Phogat
2015-06-22 17:21     ` Ben Widawsky
2015-06-22 19:49       ` Daniel Vetter
2015-06-23 23:37         ` Anuj Phogat
2015-06-24  7:33           ` Chris Wilson
2015-06-24  8:22             ` Daniel Vetter
2015-05-20 21:01 ` [PATCH 1/2] i965/gen9: Pass alignment as function parameter in drm_intel_gem_bo_alloc_internal() Anuj Phogat
2015-06-09 21:59   ` Anuj Phogat
2015-06-10  8:47     ` Damien Lespiau
2015-06-19 22:10       ` Anuj Phogat
2015-06-22 11:53         ` Daniel Vetter
2015-06-19 22:50 ` Anuj Phogat
2015-06-22 17:01   ` Ben Widawsky
2015-06-22 18:39     ` Anuj Phogat
2015-06-22 18:47 ` [PATCH v2 " Anuj Phogat
2015-06-22 19:51   ` Daniel Vetter
2015-06-22 20:04     ` Chris Wilson
2015-06-23 23:44       ` Anuj Phogat [this message]
2015-06-24  7:28         ` Chris Wilson
2015-06-24  8:24           ` Daniel Vetter
2015-06-25 18:01           ` Ben Widawsky
2015-06-25 18:11             ` Chris Wilson
2015-06-25 19:17               ` Ben Widawsky
2015-06-26 20:43                 ` Anuj Phogat
2015-07-02 19:00 ` [PATCH v3 " Anuj Phogat
2015-07-02 19:21   ` Chris Wilson
2015-07-02 21:44 ` [PATCH v4 " Anuj Phogat
2015-07-03 10:21   ` Chris Wilson

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='CAP5d04HX1To_GbdoibyVErD-4D7t-Wgy1Ee_Q=k-64FcU4cMVw@mail.gmail.com' \
    --to=anuj.phogat@gmail.com \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --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.