public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Crystal Wood <swood@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 15:41:14 -0500 (EST)	[thread overview]
Message-ID: <b65defab-53af-bc4-8681-f3f982ed6c18@redhat.com> (raw)
In-Reply-To: <e1402a544c74b508b6d2b4cc644fce5909ccd863.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]



On Fri, 9 Dec 2022, Crystal Wood wrote:

> On Fri, 2022-12-09 at 20:03 -0500, John Kacur wrote:
> > 
> > 
> > On Thu, 8 Dec 2022, Crystal Wood wrote:
> > 
> > 
> > >  
> > > @@ -677,6 +699,20 @@ static void parse_options(int argc, char *argv[])
> > >                                 exit(1);
> > >                         }
> > >                         break;
> > > +               case OPT_BUCKETWIDTH:
> > > +               case 'W':
> > > +                       g.bucket_width = strtol(optarg, NULL, 10);
> > > +                       if (g.bucket_size <= 0) {
> > 
> > I think this should be g.bucket_width
> 
> Oops
> 
> > 
> > A quick first look through and run, see the one comment above
> > near "case 'W'"
> > 
> > and then
> > 
> > checkpatch reports some minor easily fixed problems
> > 
> > ../linux/scripts/checkpatch.pl oslat.patch 
> > ERROR: code indent should use tabs where possible
> > #100: FILE: src/oslat/oslat.c:342:
> > +^I^I          g.precision, us);$
> > 
> > ERROR: code indent should use tabs where possible
> > #102: FILE: src/oslat/oslat.c:344:
> > +^I^I         g.precision, us);$
> 
> I was matching the existing style in the file that tended to use spaces for
> alignment.
> 
> > ERROR: spaces required around that '=' (ctx:VxV)
> > #227: FILE: src/oslat/oslat.c:654:
> > +       OPT_BUCKETSIZE=1, OPT_BUCKETWIDTH, OPT_CPU_LIST, 
> > OPT_CPU_MAIN_THREAD,
> >                       ^
> 
> I only added OPT_BUCKETWIDTH to the list; I didn't touch the =1 part.
> 
> -Scott
> 
> 

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.

John

  parent reply	other threads:[~2022-12-13 20:42 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 [this message]
2022-12-13 20:46       ` John Kacur
2022-12-13 22:24       ` Crystal Wood

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=b65defab-53af-bc4-8681-f3f982ed6c18@redhat.com \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=swood@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