> On Jul 16, 2018, at 4:39 PM, Darrell Ball <[email protected]> wrote:
> 
> diff --git a/lib/dpctl.man b/lib/dpctl.man
> index a75fc77..f5a36b0 100644
> --- a/lib/dpctl.man
> +++ b/lib/dpctl.man
> @@ -296,3 +296,11 @@ must be specified.  The default v4 value is 1200 and the 
> clamped minimum is
> 400.  The default v6 value is 1280, with a clamped minimum of 400, for
> testing flexibility.  The maximum frag size is not clamped, however setting
> this value too high might result in valid fragments being dropped.
> +.
> +.TP
> +\*(DX\fBipf\-set\-max\-nfrags\fR [\fIdp\fR] \fImaxfrags\fR
> +Sets the maximum number of fragments tracked by the userspace datapath
> +connection tracker.  The default value is 1000 and the clamped maximum
> +is 5000.  Note that packet buffers can be held by the fragmentation
> +module while fragments are incomplete, but will timeout after 15 seconds.
> +Memory pool sizing should be set accordingly when fragmentation is enabled.

Once the other patches go in, I'd just like to apply the incremental at the end 
of this message.

--Justin


-=-=-=-=-=-=-

diff --git a/lib/dpctl.man b/lib/dpctl.man
index 2a3b95fc94f2..39c57f6ed2f7 100644
--- a/lib/dpctl.man
+++ b/lib/dpctl.man
@@ -295,7 +295,8 @@ supported for userspace datapath.
 .TP
 \*(DX\fBipf\-set\-max\-nfrags\fR [\fIdp\fR] \fImaxfrags\fR
 Sets the maximum number of fragments tracked by the userspace datapath
-connection tracker.  The default value is 1000 and the clamped maximum
-is 5000.  Note that packet buffers can be held by the fragmentation
-module while fragments are incomplete, but will timeout after 15 seconds.
-Memory pool sizing should be set accordingly when fragmentation is enabled.
+connection tracker to \fImaxfrags\fR.  The default value is 1000 and the
+clamped maximum is 5000.  Note that packet buffers can be held by the
+fragmentation module while fragments are incomplete, but will timeout
+after 15 seconds.  Memory pool sizing should be set accordingly when
+fragmentation is enabled.  Only supported for userspace datapath.

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to