Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Feb 2004 23:09:52 +0100
From:      Andre Oppermann <oppermann@pipeline.ch>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        cvs-src@freebsd.org
Subject:   Re: cvs commit: src/sys/netinet tcp_input.c tcp_subr.c tcp_var.h
Message-ID:  <403BCBB0.4B7E1039@pipeline.ch>
References:  <200402241527.i1OFRgdm072232@repoman.freebsd.org> <403B6FBB.F1BD933C@freebsd.org> <403B7157.8030502@freebsd.org> <20040224171706.GA59202@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote:
> 
> On Tue, Feb 24, 2004 at 08:44:23AM -0700, Scott Long wrote:
> > Andre Oppermann wrote:
> > >Andre Oppermann wrote:
> > >
> > >>andre       2004/02/24 07:27:42 PST
> > >>
> > >> FreeBSD src repository
> > >>
> > >> Modified files:
> > >>   sys/netinet          tcp_input.c tcp_subr.c tcp_var.h
> > >> Log:
> > >> Convert the tcp segment reassembly queue to UMA and limit the maximum
> > >> amount of segments it will hold.
> > >>
> > >> The following tuneables and sysctls control the behaviour of the tcp
> > >> segment reassembly queue:
> > >>
> > >>  net.inet.tcp.reass.maxsegments (loader tuneable)
> > >>   specifies the maximum number of segments all tcp reassemly queues can
> > >>   hold (defaults to 1/16 of nmbclusters).
> > >>
> > >>  net.inet.tcp.reass.maxqlen
> > >>   specifies the maximum number of segments any individual tcp session
> > >>   queue
> > >>   can hold (defaults to 48).
> > >>
> > >>  net.inet.tcp.reass.cursegments (readonly)
> > >>   counts the number of segments currently in all reassembly queues.
> > >>
> > >>  net.inet.tcp.reass.overflows (readonly)
> > >>   counts how often either the global or local queue limit has been
> > >>   reached.
> > >>
> > >> Tested by:      bms, silby
> > >> Reviewed by:    bms, silby
> > >
> > >
> > >This changes sizeof(struct tcpcb) and makes a recompile of libkvm and
> > >related userland network utilities neccessary.
> > >
> >
> > Please make this statement a little louder via a HEADS UP message, and
> > add an entry to src/UPDATING.
> >
> 
> Does this require a _FreeBSD_version bump?  In other words, will
> it affect ports/{net,www,sysutils}?

No, a port doesn't need to know about before/after to adjust itself.  It
just needs to be recompiled.

-- 
Andre



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?403BCBB0.4B7E1039>