Re: [PATCH v6 25/45] trace-cmd: Read compressed trace data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 14 Jun 2021 10:50:09 +0300
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@xxxxxxxxx> wrote:

> When reading a trace.dat file of version 7, uncompress the trace data.
> The trace data for each CPU is uncompressed in a temporary file, located
> in /tmp directory with prefix "trace_cpu_data".

With large trace files, this will be an issue. Several systems setup the
/tmp directory as a ramfs file system (that is, it is locate in ram, and
not backed up on disk). If you have very large trace files, which you would
if you are going to bother compressing them, by uncompressing them into
/tmp, it could take up all the memory of the machine, or easily fill the
/tmp limit.

Simply uncompressing the entire trace data is not an option. The best we
can do is to uncompress on a as needed basis. That would require having
meta data that is stored to know what pages are compressed.

-- Steve



[Index of Archives]     [Linux USB Development]     [Linux USB Development]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux