From: Andrew Morton <akpm@linux-foundation.org>
To: "Russ Dill" <russ.dill@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Better document profile=
Date: Thu, 25 Oct 2007 16:37:43 -0700 [thread overview]
Message-ID: <20071025163743.7a3d8231.akpm@linux-foundation.org> (raw)
In-Reply-To: <f9d2a5e10710162216s149c16a3j9bb63d60fdf1e782@mail.gmail.com>
On Tue, 16 Oct 2007 22:16:47 -0700
"Russ Dill" <russ.dill@gmail.com> wrote:
> Be more explicit on what the step/bucket size accomplishes.
>
> Signed-off-by: Russ Dill <Russ.Dill@gmail.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.
next prev parent reply other threads:[~2007-10-25 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 5:16 [PATCH] Better document profile= Russ Dill
2007-10-25 23:37 ` Andrew Morton [this message]
2007-10-26 5:03 ` Russ Dill
2007-10-26 5:21 ` Andrew Morton
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=20071025163743.7a3d8231.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russ.dill@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.