All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Francisco Jerez <currojerez-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [kernel PATCH] drm/nouveau: add NOUVEAU_GEM_RELOC_HILO
Date: Wed, 12 Jan 2011 22:41:24 +0100	[thread overview]
Message-ID: <20110112214124.GA22901@joi.lan> (raw)
In-Reply-To: <87d3o1j0d4.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>

On Wed, Jan 12, 2011 at 10:08:55PM +0100, Francisco Jerez wrote:
> Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> 
> > add new relocation flag which allows to halving number of relocation
> > entries on >= nv50 cards
> >
> I suspect that this change is unnecessary. If you're actually seeing a
> performance improvement (I guess you are?), it's very likely to be

I did it for performance reasons, but actual improvement is very small (0.3%).
I sent these patches, because it's just better to do less and use less memory.

> masking the actual root of the problem -- last time I checked the nv50
> gallium pipe driver was rather careless about reloc re-submission (it
> re-submits the whole reloc chain once for every draw call instead of
> once for every pushbuf flush), and nouveau_reloc_emit() and friends are
> very unoptimized.
> 
> I'm betting that using HILO or not will make pretty much no difference
> once those two places are fixed :).

It looks they are already fixed :).

Well, you can treat these patches as data (relocations are not a bottleneck)
and forget about them.

Marcin

      parent reply	other threads:[~2011-01-12 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 20:43 [kernel PATCH] drm/nouveau: add NOUVEAU_GEM_RELOC_HILO Marcin Slusarz
     [not found] ` <1294865031-22457-1-git-send-email-marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-01-12 20:43   ` [libdrm PATCH] nouveau: optimize OUT_RELOC2 Marcin Slusarz
2011-01-12 20:43   ` [mesa PATCH] gallium/nouveau: optimize so_reloc2 Marcin Slusarz
2011-01-12 21:08   ` [kernel PATCH] drm/nouveau: add NOUVEAU_GEM_RELOC_HILO Francisco Jerez
     [not found]     ` <87d3o1j0d4.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2011-01-12 21:41       ` Marcin Slusarz [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=20110112214124.GA22901@joi.lan \
    --to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=currojerez-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.