mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/18] 2.6.17.9 perfmon2 patch for review: sampling format support
Date: Fri, 1 Sep 2006 11:09:12 -0700	[thread overview]
Message-ID: <20060901110912.e27099e8.akpm@osdl.org> (raw)
In-Reply-To: <20060901160925.GF27854@frankl.hpl.hp.com>

On Fri, 1 Sep 2006 09:09:25 -0700
Stephane Eranian <eranian@hpl.hp.com> wrote:

> > Why identify a format with a UUID rather than via a nice human-readable name?
> > 
> 
> Although a UUID is slightly more difficult to manipulate than a clear text string, it
> offers several advantages:
> 	- is guaranteed unique
> 	- generation is fully distributed
> 	- easy generation with uuidgen
> 	- fixed size
> 	- very easy to pass to the kernel, there is not char * in a struct pass to kernel
> 	- not to worry about '\0'

The kernel has got along OK using ascii strings for this sort of thing in
thousands of places for many years.  Is there something special or unique
about perfmon's requirements which make UUIDs a clearly superior
implementation?

> We use UUID to idenitfy a format + a version number. The version number can be useful
> to identify backward compatible versions of a format.

Interfaces use major and minor version numbering for that.

  reply	other threads:[~2006-09-01 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  8:05 Stephane Eranian
2006-08-23 10:31 ` Andi Kleen
2006-08-23 10:45   ` Stephane Eranian
2006-08-23 22:35 ` Andrew Morton
2006-09-01 16:09   ` Stephane Eranian
2006-09-01 18:09     ` Andrew Morton [this message]
2006-09-01 22:15       ` Stephane Eranian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060901110912.e27099e8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome