nouveau_bo_busy not supported in kernel anymore

nouveau_bo_busy not supported in kernel anymore

[Lucas Stach]

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

Re: nouveau_bo_busy not supported in kernel anymore

[Francisco Jerez]

[-- Attachment #1.1.1: Type: text/plain, Size: 453 bytes --]

Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org> writes:

> 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.

It doesn't, it just removes the NOBLOCK flag, because it's the default
(and only) behavior now.

>[...]

[-- Attachment #1.2: Type: application/pgp-signature, Size: 229 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

Re: nouveau_bo_busy not supported in kernel anymore

[Lucas Stach]

Ok, so some people including me just misunderstood the commit. Thanks
for the enlightenment.

-- lynxeye

Am Montag, den 20.12.2010, 22:39 +0100 schrieb Francisco Jerez: 
> Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org> writes:
> 
> > 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.
> 
> It doesn't, it just removes the NOBLOCK flag, because it's the default
> (and only) behavior now.
> 
> >[...]