From: Crystal Wood <swood@redhat.com>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
rt-users <linux-rt-users@vger.kernel.org>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH] oslat: Add command line option for bucket width
Date: Tue, 13 Dec 2022 16:24:14 -0600 [thread overview]
Message-ID: <2dc379a7d42d8f758e7d6eeacdae0a1ef632d517.camel@redhat.com> (raw)
In-Reply-To: <b65defab-53af-bc4-8681-f3f982ed6c18@redhat.com>
On Tue, 2022-12-13 at 15:41 -0500, John Kacur wrote:
> One more thing that we just saw, if you run oslat without any options,
> just the defaults you get 32 buckets with the highest one being 32us
>
> But if you run
> oslat -W 500
>
> You still get 32 buckets but since the width is half, then largest bucket
> is 32us
>
> This increases the resolution of the buckets, but it puts all the overflow
> in the 16us buckets, wondering if we should double the number of buckets
> so that the largest one is still 32us ?
>
> I realize you could do
> oslat -b 64 -W 500
> to achieve that, but perhaps the default is not good like this.
Sounds reasonable.
-Scott
prev parent reply other threads:[~2022-12-13 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 5:22 [PATCH] oslat: Add command line option for bucket width Crystal Wood
2022-12-10 1:03 ` John Kacur
2022-12-10 1:40 ` Crystal Wood
2022-12-13 19:31 ` John Kacur
2022-12-13 22:21 ` Crystal Wood
2022-12-13 20:41 ` John Kacur
2022-12-13 20:46 ` John Kacur
2022-12-13 22:24 ` Crystal Wood [this message]
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=2dc379a7d42d8f758e7d6eeacdae0a1ef632d517.camel@redhat.com \
--to=swood@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).