On Thu, Jan 26, 2012 at 01:28:16AM +0200, Sakari Ailus wrote: > Why you "should not hang onto mappings forever"? This is currently done by > virtually all V4L2 drivers where such mappings are relevant. Not doing so > would really kill the performance i.e. it's infeasible. Same goes to (m)any > other multimedia devices dealing with buffers containing streaming video > data.
Because I want dynamic memory managemt simple because everything else does not make sense. I know that in v4l things don't work that way, but in drm they _do_. And if you share tons of buffers with drm drivers and don't follow the rules, the OOM killer will come around and shot at your apps. Because at least in i915 we do slurp in as much memory as we can until the oom killer starts growling, at which point we kick out stuff. I know that current dma_buf isn't there and for many use-cases discussed here we can get away without that complexity. So you actually can just map your dma_buf and never ever let go of that mapping again in many cases. The only reason I'm such a stuborn bastard about all this is that drm/* will do dynamic bo management even with dma_buf sooner or later and you should better know that and why and the implications if you choose to ignore it. And obviously, the generic dma_buf interface needs to be able to support it. Cheers, Daniel -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
