aboutsummaryrefslogtreecommitdiff
path: root/sys/netinet/tcp_reass.c
diff options
context:
space:
mode:
authorGleb Smirnoff <glebius@FreeBSD.org>2017-05-10 23:32:31 +0000
committerGleb Smirnoff <glebius@FreeBSD.org>2017-05-10 23:32:31 +0000
commit7637c57ee1163ec5c9e8ad70173fbbdcfafd2088 (patch)
tree62f9d4e88e6902e6e5a7d4d1398dff0a2a13fb86 /sys/netinet/tcp_reass.c
parentcac6fd1154811b24f3899a8f9e07c0140542a90d (diff)
downloadsrc-7637c57ee1163ec5c9e8ad70173fbbdcfafd2088.tar.gz
src-7637c57ee1163ec5c9e8ad70173fbbdcfafd2088.zip
There is no good reason for TCP reassembly zone to be UMA_ZONE_NOFREE.
It has strong locking model, doesn't have any timers associated with entries. The entries theirselves are referenced only from the tcpcb zone, which itself is a normal zone, without the UMA_ZONE_NOFREE flag.
Notes
Notes: svn path=/head/; revision=318166
Diffstat (limited to 'sys/netinet/tcp_reass.c')
-rw-r--r--sys/netinet/tcp_reass.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/netinet/tcp_reass.c b/sys/netinet/tcp_reass.c
index 163dba3d6490..7f73a240e9cc 100644
--- a/sys/netinet/tcp_reass.c
+++ b/sys/netinet/tcp_reass.c
@@ -108,7 +108,7 @@ tcp_reass_global_init(void)
TUNABLE_INT_FETCH("net.inet.tcp.reass.maxsegments",
&tcp_reass_maxseg);
tcp_reass_zone = uma_zcreate("tcpreass", sizeof (struct tseg_qent),
- NULL, NULL, NULL, NULL, UMA_ALIGN_PTR, UMA_ZONE_NOFREE);
+ NULL, NULL, NULL, NULL, UMA_ALIGN_PTR, 0);
/* Set the zone limit and read back the effective value. */
tcp_reass_maxseg = uma_zone_set_max(tcp_reass_zone,
tcp_reass_maxseg);