* nouveau_bo_busy not supported in kernel anymore @ 2010-12-20 21:20 Lucas Stach 2010-12-20 21:39 ` Francisco Jerez 0 siblings, 1 reply; 3+ messages in thread From: Lucas Stach @ 2010-12-20 21:20 UTC (permalink / raw) To: Nouveau Dev List; +Cc: Ben Skeggs 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: nouveau_bo_busy not supported in kernel anymore 2010-12-20 21:20 nouveau_bo_busy not supported in kernel anymore Lucas Stach @ 2010-12-20 21:39 ` Francisco Jerez [not found] ` <87sjxs2kg2.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: Francisco Jerez @ 2010-12-20 21:39 UTC (permalink / raw) To: Lucas Stach; +Cc: Nouveau Dev List, Ben Skeggs [-- 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <87sjxs2kg2.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>]
* Re: nouveau_bo_busy not supported in kernel anymore [not found] ` <87sjxs2kg2.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org> @ 2010-12-20 22:26 ` Lucas Stach 0 siblings, 0 replies; 3+ messages in thread From: Lucas Stach @ 2010-12-20 22:26 UTC (permalink / raw) To: Francisco Jerez; +Cc: Nouveau Dev List, Ben Skeggs 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. > > >[...] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-12-20 22:26 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-12-20 21:20 nouveau_bo_busy not supported in kernel anymore Lucas Stach 2010-12-20 21:39 ` Francisco Jerez [not found] ` <87sjxs2kg2.fsf-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org> 2010-12-20 22:26 ` Lucas Stach
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.