From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2] tc-sfq: update man page
Date: Tue, 31 Jan 2012 13:38:28 +0100 [thread overview]
Message-ID: <4F27E0C4.1050609@computer.org> (raw)
In-Reply-To: <1327411778.7231.10.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On 01/24/2012 02:29 PM, Eric Dumazet wrote:
> Add documentation about RED mode, and new parameters (flows, depth)
> added in linux 3.3
>
> Signed-off-by: Eric Dumazet<eric.dumazet@gmail.com>
> ---
> man/man8/tc-sfq.8 | 127 +++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 108 insertions(+), 19 deletions(-)
>
> diff --git a/man/man8/tc-sfq.8 b/man/man8/tc-sfq.8
> index e177f56..5a651ff 100644
> --- a/man/man8/tc-sfq.8
> +++ b/man/man8/tc-sfq.8
...
+Source and Destination port
> .P
> If these are available. SFQ knows about ipv4 and ipv6 and also UDP, TCP and ESP.
> Packets with other protocols are hashed based on the 32bits representation of their
> -destination and the socket they belong to. A flow corresponds mostly to a TCP/IP
> -connection.
> +destination and source. A flow corresponds mostly to a TCP/IP connection.
Don't understand this. Did you want to replace "connection" by
"destination and source"? Do you mean that a "connection" is
characterised by source and destination?
next prev parent reply other threads:[~2012-01-31 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 13:29 [PATCH iproute2] tc-sfq: update man page Eric Dumazet
2012-01-31 12:38 ` Jan Ceuleers [this message]
2012-01-31 15:28 ` Eric Dumazet
2012-01-31 20:11 ` Jan Ceuleers
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=4F27E0C4.1050609@computer.org \
--to=jan.ceuleers@computer.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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.