From: Andi Kleen <ak@muc.de>
To: Glen Turner <glen.turner@aarnet.edu.au>
Cc: netdev@oss.sgi.com
Subject: network manpages was Re: is UDP_CORK "real"
Date: 27 Apr 2005 14:26:48 +0200
Date: Wed, 27 Apr 2005 14:26:48 +0200 [thread overview]
Message-ID: <20050427122648.GA12597@muc.de> (raw)
In-Reply-To: <426F2A1D.10001@aarnet.edu.au>
On Wed, Apr 27, 2005 at 03:28:53PM +0930, Glen Turner wrote:
> Please mail me with what you think is required here. I've
> been getting grief from our high performance users on
> exactly this point (and the sysctl maze of twisty options)
sysctl is mostly documented in Documentation/*.
Also the sysctls change sometimes, so I am not sure it is a good idea
to put them into the manpages which are supposed to be more version
independent. At least I would only put the more important ones there.
In particular the ipv6 protocol manpage needs a rewrite, it was only a
relatively poor quick&dirty job. For the others it would be probably
sufficient to just check what new ioctls/socket options are missing
and document them and perhaps check if the NOTES/BUGS caveats still
apply. An sctp manpage is also lacking I think, that was a completely
new protocol.
It would be nice of course if David could enforce a policy
to require a manpage patch for new ioctls/socket options etc.
in the future, then such documentation lag would not happen.
-Andi
next prev parent reply other threads:[~2005-04-27 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 23:14 is UDP_CORK "real" Rick Jones
2005-04-21 23:25 ` David S. Miller
2005-04-21 23:53 ` Rick Jones
2005-04-26 13:40 ` Andi Kleen
2005-04-27 8:20 ` Michael Kerrisk
[not found] ` <426F2A1D.10001@aarnet.edu.au>
2005-04-27 12:26 ` Andi Kleen [this message]
2005-04-27 18:43 ` network manpages was " David S. Miller
2005-04-29 15:29 ` Andi Kleen
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=20050427122648.GA12597@muc.de \
--to=ak@muc.de \
--cc=glen.turner@aarnet.edu.au \
--cc=netdev@oss.sgi.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).