On Feb 9, 2019, at 12:13 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
On Fri, Feb 08, 2019 at 08:44:32PM -0800, Mark D Rustad wrote:On Feb 8, 2019, at 2:54 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt index 2ea4c45cf1c8..7c229f59016f 100644 --- a/Documentation/networking/ip-sysctl.txt +++ b/Documentation/networking/ip-sysctl.txt @@ -112,14 +112,11 @@ min_adv_mss - INTEGER IP Fragmentation: -ipfrag_high_thresh - INTEGER - Maximum memory used to reassemble IP fragments. When - ipfrag_high_thresh bytes of memory is allocated for this purpose, - the fragment handler will toss packets until ipfrag_low_thresh - is reached. This also serves as a maximum limit to namespaces - different from the initial one. - -ipfrag_low_thresh - INTEGER +ipfrag_high_thresh - LONG INTEGER + Maximum memory used to reassemble IP fragments. + +ipfrag_low_thresh - LONG INTEGER + (Obsolete since linux-4.17)It seems very strange to say that it is obsolete since 4.17 in a 4.4 kernel.4.17 is a point in time :)
Of course I understand, but some random non-kernel-developer tuning a kernel may be pretty puzzled. I don't know right off the top something brief that would be more generally meaningful, but maybe someone might. What does obsolete mean in this context? It exists but does nothing? It exists and does something but will eventually go away?
-- Mark Rustad, MRustad@xxxxxxxxx
Attachment:
signature.asc
Description: Message signed with OpenPGP
