linux-kernel - Re: [PATCH 1/1 net-next] ipv4: add kernel parameter tcpmhash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20141104143249.608c9fe4@lwn.net>
Date:	Tue, 4 Nov 2014 14:32:49 -0500
From:	Jonathan Corbet <corbet@....net>
To:	Fabian Frederick <fabf@...net.be>
Cc:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/1 net-next] ipv4: add kernel parameter
 tcpmhash_entries

On Tue,  4 Nov 2014 20:23:08 +0100
Fabian Frederick <fabf@...net.be> wrote:

> +			Set tcp_metrics_hash slot number.

So I'm not entirely clear on what that means.  Did you mean "Set the
number of tcp_metrics_hash slots"?  If so, that wording should be used.

Even in that case, though, what does this parameter actually *mean*?  If
we're going to document the parameter (and I think we should), it would
be good to say why a user might want to change it and what effects they
would expect to see.

Care to redo with that in mind?

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/