linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [patch 2/2] Add queuelat manpage
Date: Wed, 19 Sep 2018 16:41:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1809191640160.6250@planxty> (raw)
In-Reply-To: <20180904115701.634017140@redhat.com>



On Tue, 4 Sep 2018, Marcelo Tosatti wrote:

> Add a man page for queuelat, with a short introduction
> and description for each option.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> 
> ---
>  src/queuelat/queuelat.8 |   59 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 59 insertions(+)
> 
> Index: rt-tests/src/queuelat/queuelat.8
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ rt-tests/src/queuelat/queuelat.8	2018-09-03 17:55:39.956071513 -0300
> @@ -0,0 +1,59 @@
> +.\"                                      Hey, EMACS: -*- nroff -*-
> +.TH QUEUELAT 8 "Sept 3, 2018"
> +.\" Please adjust this date whenever revising the manpage.
> +.\"
> +.\" Some roff macros, for reference:
> +.\" .nh        disable hyphenation
> +.\" .hy        enable hyphenation
> +.\" .ad l      left justify
> +.\" .ad b      justify to both left and right margins
> +.\" .nf        disable filling
> +.\" .fi        enable filling
> +.\" .br        insert line break
> +.\" .sp <n>    insert n+1 empty lines
> +.\" for manpage-specific macros, see man(7)
> +.SH NAME
> +queuelat \- Queue latency test program
> +.SH SYNOPSIS
> +.B queuelat
> +.RI "[\-h] [\-m " max-queue-len "] [\-c " cycles-per-packet "] [\-p " mpps "] [\-f " tsc-freq "] [\-t " timeout "] \
> +
> +.SH DESCRIPTION
> +queuelat simulates a network queue checking for latency
> +violations in packet processing.
> +
> +.SH OPTIONS
> +A summary of options is included below.
> +.TP
> +.B \-h
> +Show help
> +.br
> +.TP
> +.B \-m max-queue-len
> +Maximum allowed latency, in nanoseconds. If latency to process
> +.br
> +any packet exceeds this value, the program quits,
> +writing
> +.br
> +a message to the trace buffer.
> +.TP
> +.B \-c cycles-per-packet
> +Estimated number of cycles it takes to process one packet.
> +.br
> +This value should come from the envisioned packet
> +.br
> +forwarding application being simulated.
> +.TP
> +.B \-p mpps
> +Million packets per second that arrive for processing.
> +.TP
> +.B \-f tsc-freq-mhz
> +TSC frequency in MHz.
> +.TP
> +.B \-t timeout
> +Timeout in seconds to quit the program.
> +
> +
> +.SH AUTHOR
> +queuelat was written by Marcelo Tosatti <mtosatti@redhat.com>
> +.br
> 
> 
> 

Signed-off-by: John Kacur <jkacur@redhat.com>

      parent reply	other threads:[~2018-09-19 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180904115633.410153367@redhat.com>
     [not found] ` <20180904115700.461458689@redhat.com>
2018-09-19 14:39   ` [patch 1/2] add -h option to queuelat John Kacur
     [not found] ` <20180904115701.634017140@redhat.com>
2018-09-19 14:41   ` John Kacur [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=alpine.LFD.2.21.1809191640160.6250@planxty \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mtosatti@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).