On Wed, Jun 27, 2012 at 1:24 PM, Jason Garrett-Glaser <[email protected]> wrote: > On Wed, Jun 27, 2012 at 12:29 PM, Daniel Kang <[email protected]> wrote: >> Now, memory is allocated for each macroblock in the frame. >> >> Previously, there was an optimization to only need width+height*2+1 >> macroblocks allocated. > > I strongly dislike this patch. Can we implemented sliced threading -- > a rarely-used feature -- without slowing down the most common case? > > Jason
I see, you removed it and then added it back later. This is a lot of redundant and confusing git history; if you're going to add it back in anyways, can you merge it back so that it never gets removed in the first place? Jason _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
