| 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
| ||
|
Message-ID: <20070607073021.GA21139@elte.hu> Date: Thu, 7 Jun 2007 09:30:21 +0200 From: Ingo Molnar <mingo@...e.hu> To: Martin Peschke <mp3@...ibm.com> Cc: "Bill Huey (hui)" <billh@...ppy.monkey.org>, linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl, jbaron@...hat.com, rostedt@...dmis.org, linux-s390@...r.kernel.org Subject: Re: [RFC] [Patch 4/4] lock contention tracking slimmed down * Martin Peschke <mp3@...ibm.com> wrote: > Bill Huey (hui) wrote: > > There are roughly about 400 locks in a normal kernel for a desktop. The > > list is rather cumbersome anyways so, IMO, it really should be handled > > by parsing tools, etc... There could be more properties attached to each > > lock especially if you intend to get this to work on -rt which need more > > things reported. > > Adding stuff to an already wide table in a readable fashion is more > difficult than making a list longer. > > Do mean I might submit this stuff for -rt? Firstly, submit cleanup patches that _do not change the output_. If you have any output changes, do it as a separate patch, ontop of the cleanup patch. Mixing material changes and cleanups into a single patch is a basic patch submission mistake that will only earn you NACKs. Ingo - 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