[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <870EE9C6-3748-498C-B6E8-33724168C605@gmail.com>
Date: Fri, 8 Feb 2019 20:44:32 -0800
From: Mark D Rustad <mrustad@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: Linux 4.4.174
On Feb 8, 2019, at 2:54 AM, Greg KH <gregkh@...uxfoundation.org> 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.
> Maximum memory used to reassemble IP fragments before the kernel
> begins to remove incomplete fragment queues to free up resources.
> The kernel still accepts new fragments for defragmentation.
--
Mark Rustad, MRustad@...il.com
Download attachment "signature.asc" of type "application/pgp-signature" (874 bytes)
Powered by blists - more mailing lists