Re: [PATCH] trace-cmd: Try alternate path for message cache
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] trace-cmd: Try alternate path for message cache
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Fri, 1 Apr 2022 19:06:29 -0400
- Cc: linux-trace-devel@xxxxxxxxxxxxxxx, rostedt@xxxxxxxxxx, vineethrp@xxxxxxxxxx, Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx>
- In-reply-to: <CAEXW_YQxPgaKOMhDy8kVdaT9esvY8ctP1Mfw3RZXwkJkTYhh0w@mail.gmail.com>
- References: <20220329191801.429691-1-joel@joelfernandes.org> <20220401153737.7c444426@gandalf.local.home> <CAEXW_YQxPgaKOMhDy8kVdaT9esvY8ctP1Mfw3RZXwkJkTYhh0w@mail.gmail.com>
On Fri, 1 Apr 2022 15:50:10 -0400
Joel Fernandes <joel@xxxxxxxxxxxxxxxxx> wrote:
> export TRACECMD_TEMPDIR="/data"
>
> That’s fair. What about using memfd for this, do you feel that’s
> reasonable? I have not yet measured how big this file gets but if it’s
> small enough that might work too.
Is this a separate question? That is, do you mean using the above
environment variable *and* then use memfd?
I believe that the cache is used for passing the compressed data from the
guest to the host. I don't think it will be more than one compressed chunk.
But Tzvetomir would know better.
-- Steve
[Index of Archives]
[Linux USB Development]
[Linux USB Development]
[Linux Audio Users]
[Yosemite Hiking]
[Linux Kernel]
[Linux SCSI]