On 02/03/17 18:45, Tobias Droste wrote:
Hi Timothy,
if you plan to support multiple compression algorithms, shouldn't "struct
cache_entry_file_data" contain some info about what compression algorithm was
used to compress the data? Or is this already there and I missed it?
I don't plan to support more than one. I'm just saying it's a
possibility for the future, depending on further analysis and
requirements from different hardware. But right now I would just like to
land zlib support so we have a baseline to work from.
Am Donnerstag, 2. März 2017, 03:20:05 CET schrieb Matt Turner:
On Wed, Mar 1, 2017 at 2:19 PM, Timothy Arceri <tarc...@itsqueeze.com>
wrote:
IMO we should go with zlib and people can provide future patches with
justifications/stats for using a different library over zlib just like we
do for any other performance based patch.
Yes, agreed. "Which compression should we use?" is one of the easiest
bikesheds to paint.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
