lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Wed, 8 Oct 2014 10:26:14 +0100
From:	sabra gargouri <sabra3982@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: ftrace: trace buffer size configuration

Hi,

I'am using ftrace to trace my system for a few minutes. For that I
configured the trace buffer via buffer_size_kb file to 100000 kb so 200000
for 2 CPUs. After tracing my system the trace size is 500MB.
Why the allocated size for the trace buffer (200 MB) is not the same of the
trace file (500 MB) ?

and is it convenient to allocate such a big size for the buffer?

Best regards
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ