Re: [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data

2013-06-05 Thread Aruna Balakrishnaiah
Hi Ben, There is no change in this patchset and it applies cleanly on top of v4 of Nvram-to-pstorepatches. The patchset takes care of compressing oops messages while writing to NVRAM, so that more oops data can be captured in the given space. big_oops_buf (2.22 * oops_data_sz) is allocated

Re: [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data

2013-06-05 Thread Aruna Balakrishnaiah
Hi Ben, There is no change in this patchset and it applies cleanly on top of v4 of Nvram-to-pstorepatches. The patchset takes care of compressing oops messages while writing to NVRAM, so that more oops data can be captured in the given space. big_oops_buf (2.22 * oops_data_sz) is allocated

[RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data

2013-04-26 Thread Aruna Balakrishnaiah
The patchset takes care of compressing oops messages while writing to NVRAM, so that more oops data can be captured in the given space. big_oops_buf (2.22 * oops_data_sz) is allocated for compression. oops_data_sz is oops header size less of oops partition size. Pstore will internally call

[RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data

2013-04-26 Thread Aruna Balakrishnaiah
The patchset takes care of compressing oops messages while writing to NVRAM, so that more oops data can be captured in the given space. big_oops_buf (2.22 * oops_data_sz) is allocated for compression. oops_data_sz is oops header size less of oops partition size. Pstore will internally call