On Thu, Aug 29, 2013 at 10:58:37AM +0800, WANG Chao wrote: > Hi, Cliff > > On 08/28/13 at 05:08pm, Cliff Wickman wrote: > > From: Cliff Wickman <cpw at sgi.com> > > > > Reverse the meanings of -c (compression) and -p (snappy compression) if > > USESNAPPY is defined. > > > > The distro kdump scripts seem to only support -c for compression. > > So make -c mean snappy compression if it is supported. > > It looks like more a distro issue to me. I'm wondering if that script > only support -c, why do that distro compile makedumpfile with USESNAPPY? > > I don't think other distros would like to see this change. IMHO, the > right thing to do is fix that kdump script on that particular distro, > not reverse -c and -p. > > Thanks > WANG Chao I agree that some distros could easily change their default compression choice, for example -c to -p in RHEL's /etc/kdump.conf. But on the other hand SLES11 just uses KDUMP_DUMPFORMAT="compressed" in /etc/sysconfig/kdump. Translation to -c occurs somewhere under the covers. Makedumpfile could change the default meaning of "compressed" to snappy compression on the grounds that we know snappy to be much faster than zlib compression. And so we default to it if available. You would in that way make the intelligent choice without administrative intervention. (You would also have to assume that crash is also be built snappy-capable for a system that supports snappy compression.) I could see it either way. I find this patch a convenient way to make the choice. -Cliff -- Cliff Wickman SGI cpw at sgi.com (651) 683-3824
