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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1263990868-8119-1-git-send-email-sgruszka@redhat.com>
Date:	Wed, 20 Jan 2010 13:34:22 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Oleg Nesterov <oleg@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	Balbir Singh <balbir@...ibm.com>, linux-kernel@...r.kernel.org,
	Stanislaw Gruszka <sgruszka@...hat.com>
Subject: [PATCH 0/6 -mm] cpu-timers patches

Here are patches for cpu-timers I mainly wrote to not call 
thread_group_cputime() in fastpath_timer_check(), which we
discuss in this thread:

http://thread.gmane.org/gmane.linux.kernel/909349/focus=912327
  
On the way I fix some other bugs (SIGEV_NONE timer, old increase value
in timer_settime()) and do other cleanups and optimizations, patch 5
however increase time when sighand->siglock is held. 

Compared with previous send of patches as RFC, I rebased them to -mm
tree, change some changelogs and do some minor code changes.

[PATCH 1/6 -mm] cpu-timers: simplify RLIMIT_CPU handling
[PATCH 2/6 -mm] cpu-timers: cleanup arm_timer()
[PATCH 3/6 -mm] cpu-timers: return correct previous timer reload value
[PATCH 4/6 -mm] cpu-timers: change SIGEV_NONE timer implementation
[PATCH 5/6 -mm] cpu-timers: assure to not iterate over all threads in fastpath_timer_check()
[PATCH 6/6 -mm] cpu-timers: optimize run_posix_cpu_timers()

Cheers
Stanislaw

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