linux-kernel - [PATCH 0/2] Some cleanup of ring buffer benchmark

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1436454561-29925-1-git-send-email-pmladek@suse.com>
Date:	Thu,  9 Jul 2015 17:09:19 +0200
From:	Petr Mladek <pmladek@...e.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Jiri Kosina <jkosina@...e.cz>, Ingo Molnar <mingo@...nel.org>,
	linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>
Subject: [PATCH 0/2] Some cleanup of ring buffer benchmark

I send two patches that are side effect of my quest for a better
kthread API. They are not super important but I hope that you find
them useful.

The first patch helped me to get rid of an operation outside the
main cycle. It makes the code cleaner anyway.

The second patch improves my previous commit. The race is not
critical. It would just delay the rmmod. Anyway, I am getting
more familiar with all the possible problems around scheduling
and I hope that I see it better now.

PS: I have vacation the following two weeks and probably won't
be able to answer potential questions in the meantime. These
two patches are part of a bigger patch set that I will send
after vacation. If they get integrated, it would be nice.
Sigh, I have bad timing these days.

Petr Mladek (2):
  ring_buffer: Initialize completions statically in the benchmark
  ring_buffer: Fix more races when terminating the producer in the
    benchmark

 kernel/trace/ring_buffer_benchmark.c | 77 ++++++++++++++++++------------------
 1 file changed, 39 insertions(+), 38 deletions(-)

-- 
1.8.5.6

--
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/