All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mashak <mrv@mojatatu.com>
To: peng yu <yupeng0921@gmail.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, phil@nwl.cc
Subject: Re: [iproute PATCH] ss: add detail explains of -m, -o, -e and -i options in ss man page
Date: Wed, 25 Oct 2017 11:06:08 -0400	[thread overview]
Message-ID: <8560b3clnj.fsf@mojatatu.com> (raw)
In-Reply-To: <CAG3TDc0XxtkA5TU_GDzdZv1ujuqf09e9kBYQm2p5QGbppt7efw@mail.gmail.com> (peng yu's message of "Tue, 24 Oct 2017 17:13:30 -0700")

peng yu <yupeng0921@gmail.com> writes:

> commit 340a45f79395144bd14fdf9be1904c0036456b6e
> Author: yupeng <yupeng0921@gmail.com>
> Date:   Tue Oct 24 23:55:29 2017 +0000
>
>     add additional explain in ss man page
>
>     Add detail explains of -m, -o, -e and -i options, which are not
> documented anywhere
>
>     Signed-off-by: Peng Yu <yupeng0921@gmail.com>
>
> diff --git a/man/man8/ss.8 b/man/man8/ss.8
> index 3bec97f..4597733 100644
> --- a/man/man8/ss.8
> +++ b/man/man8/ss.8
> @@ -176,6 +176,147 @@ states except for
>  - opposite to
>  .B bucket
>
> +.SH Additional explain of -m, -o, -e and -i options
> +Some fields may have different meanings if the netowrk protocl is
> different. Below explain focus on tcp protocol.
> +.TP
> +.B -m option
> +skmem:(r<rmem_alloc>,rb<rcv_buf>,t<wmem_alloc>,tb<snd_buf>,f<fwd_alloc>,w<wmem_queued>,o<opt_mem>,bl<back_log>)
> +
> +.B <rmem_alloc>
> +the memory allocated for receiving package
> +

Need to change 'package' to 'packet' in multiple places.

[...]

  parent reply	other threads:[~2017-10-25 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  0:13 [iproute PATCH] ss: add detail explains of -m, -o, -e and -i options in ss man page peng yu
2017-10-25  6:37 ` Stephen Hemminger
2017-10-25 15:06 ` Roman Mashak [this message]
2017-10-25 21:20   ` peng yu
2017-10-25 21:52     ` Phil Sutter
2017-10-26  7:15       ` [PATCH] add additional explain " yupeng
2017-10-26  9:36         ` Phil Sutter

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=8560b3clnj.fsf@mojatatu.com \
    --to=mrv@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=stephen@networkplumber.org \
    --cc=yupeng0921@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.