[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3ece790808161340x4b03b91er6f0bfcc46c6fb3ad@mail.gmail.com>
Date: Sat, 16 Aug 2008 13:40:50 -0700
From: "Tim Hockin" <thockin@...kin.org>
To: schwidefsky@...ibm.com
Cc: "Rusty Russell" <rusty@...tcorp.com.au>,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
lf_kernel_messages@...ts.linux-foundation.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Michael Holzheu" <holzheu@...ibm.com>,
"Gerrit Huizenga" <gh@...ibm.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
"Jan Kara" <jack@...e.cz>, "Pavel Machek" <pavel@....cz>,
"Sam Ravnborg" <sam@...nborg.org>, "Joe Perches" <joe@...ches.com>,
"Jochen Voß" <jochen.voss@...glemail.com>,
"Kunai Takashi" <kunai@...ux-foundation.jp>,
"Tim Bird" <tim.bird@...sony.com>
Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros.
On Sat, Aug 16, 2008 at 10:49 AM, Martin Schwidefsky
<schwidefsky@...ibm.com> wrote:
>> > > Can you hash the format string to generate the id? 6 hex digits should
>> > > be enough, and your tool can check for clashes. As it's bad form to have
>> > > identical strings for different semantics anyway, this seems to make
>> > > sense.
> Ok, so a specialized version of printk will do the work to calculate
> the hash. Only, what will we do if there ever is a conflict? The message
> tag has to be unique. The shorter the hash is, the more likely a
> collision gets. Don't know if 6 hash digits is enough to just ignore the
> problem.
And if you ever need to change the text that is in the format string?
The hash changes. That seems exactly counter to your goal...
Tim
--
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