On Mon, Jun 13, 2011 at 07:28:50AM -0700, Arjan van de Ven wrote: > On Sun, 12 Jun 2011 16:07:07 -0700 > "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx> wrote: > > > > > > the codec issue seems to be solved in time; a previous generation > > > silicon on our (Intel) side had ARM ecosystem blocks that did not do > > > scatter gather, however the current generation ARM ecosystem blocks > > > all seem to have added S/G to them.... > > > (in part this is coming from the strong desire to get camera/etc > > > blocks to all use "GPU texture" class memory, so that the camera > > > can directly deposit its information into a gpu texture, and > > > similar for media encode/decode blocks... this avoids copies as > > > well as duplicate memory). > > > > That is indeed a clever approach! > > > > Of course, if the GPU textures are in main memory, there will still > > be memory consumption gains to be had as the image size varies (e.g., > > displaying image on one hand vs. menus and UI on the other). > > graphics drivers and the whole graphics stack is set up to deal with > that... textures aren't per se "screen size", the texture for a button > is only as large as the button (with some rounding up to multiples of > some small power of two) In addition, I would expect that for quite some time there will continue to be a lot of systems with display hardware a bit too simple to qualify as "GPU". Thanx, Paul -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>