[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071025163743.7a3d8231.akpm@linux-foundation.org>
Date: Thu, 25 Oct 2007 16:37:43 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Russ Dill" <russ.dill@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Better document profile=
On Tue, 16 Oct 2007 22:16:47 -0700
"Russ Dill" <russ.dill@...il.com> wrote:
> Be more explicit on what the step/bucket size accomplishes.
>
> Signed-off-by: Russ Dill <Russ.Dill@...il.com>
> ---
> Documentation/kernel-parameters.txt | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> index eb24799..3c6fd27 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1427,7 +1427,10 @@ and is between 256 and 4096 characters. It is
> defined in the file
Your email client is wordwrapping the patches.
> Format: [schedule,]<number>
> Param: "schedule" - profile schedule points.
> Param: <number> - step/bucket size as a power of 2 for
> - statistical time based profiling.
> + statistical time based profiling. A value of
> + 2 will provide a granularity of 4 bytes, a
> + value of 3 will provide a granularity of 8
> + bytes and so on.
> Param: "sleep" - profile D-state sleeping (millisecs)
Actually the prof_shift isn't in units of bytes: it is in units of
sizeof(unsigned long).
So on a 64-bit kernel, prof_shift=2 will give a granularity of 8<<2 bytes
and on a 32-bit kernel, prof_shift=3 will give a granularity of 4<<3 bytes.
-
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