All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
To: Nouveau Dev List
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: nouveau_bo_busy not supported in kernel anymore
Date: Mon, 20 Dec 2010 22:20:35 +0100	[thread overview]
Message-ID: <1292880035.3094.266.camel@workstation> (raw)

Hi all,

I want to bring up this issue again on the mailing list, since it got
lost in some irc chat a few days ago.

Deadwood came to the channel and noted that
25ee1f0e25195729f28b15f33d74db9ec6afd696 removes support for
NOUVEAU_GEM_CPU_PREP_NOBLOCK in the kernel. This renders nouveau_bo_busy
quite useless.

Since nvfx depends on this function to avoid render serialization in the
fragment shader code we should either revert the commit, or if there are
valid reasons to remove the kernel support, rewrite the frag shader path
in nvfx.

Also radeon guys use some similar logic in their caching buffer manager
to implement buffer reuse, which seems to be a possible worthwhile
optimization for nvfx.

Darktama, can you please comment on the reasons for the kernel change?

-- lynxeye

             reply	other threads:[~2010-12-20 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 21:20 Lucas Stach [this message]
2010-12-20 21:39 ` nouveau_bo_busy not supported in kernel anymore Francisco Jerez
     [not found]   ` <87sjxs2kg2.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2010-12-20 22:26     ` Lucas Stach

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=1292880035.3094.266.camel@workstation \
    --to=dev-8ppwabl0hbeelga04laivw@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@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.