netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Bernat <vincent@bernat.im>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	linux-doc@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: [PATCH net-next] tcp: more documentation for tcp_tw_reuse and tcp_tw_recycle
Date: Sun,  4 May 2014 11:41:38 +0200	[thread overview]
Message-ID: <1399196499-8449-1-git-send-email-vincent@bernat.im> (raw)

Hi!

I think this is not the first tentative to try to complete the
documentation of tcp_tw_reuse and tcp_tw_recycle. Last one was 4 years
ago I think. Here is another one which tries to stay short, warns
about the dangers of recycling and which kind of connections are
affected. The general warning is kept.

             reply	other threads:[~2014-05-04  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  9:41 Vincent Bernat [this message]
2014-05-04  9:41 ` [PATCH] tcp: more documentation for tcp_tw_reuse and tcp_tw_recycle Vincent Bernat
2014-05-07 19:16   ` David Miller
2014-05-07 19:55     ` Vincent Bernat

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=1399196499-8449-1-git-send-email-vincent@bernat.im \
    --to=vincent@bernat.im \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).