Conrad Meyer 7790c8c199 Split out a more generic debugnet(4) from netdump(4)
Debugnet is a simplistic and specialized panic- or debug-time reliable
datagram transport.  It can drive a single connection at a time and is
currently unidirectional (debug/panic machine transmit to remote server
only).

It is mostly a verbatim code lift from netdump(4).  Netdump(4) remains
the only consumer (until the rest of this patch series lands).

The INET-specific logic has been extracted somewhat more thoroughly than
previously in netdump(4), into debugnet_inet.c.  UDP-layer logic and up, as
much as possible as is protocol-independent, remains in debugnet.c.  The
separation is not perfect and future improvement is welcome.  Supporting
INET6 is a long-term goal.

Much of the diff is "gratuitous" renaming from 'netdump_' or 'nd_' to
'debugnet_' or 'dn_' -- sorry.  I thought keeping the netdump name on the
generic module would be more confusing than the refactoring.

The only functional change here is the mbuf allocation / tracking.  Instead
of initiating solely on netdump-configured interface(s) at dumpon(8)
configuration time, we watch for any debugnet-enabled NIC for link
activation and query it for mbuf parameters at that time.  If they exceed
the existing high-water mark allocation, we re-allocate and track the new
high-water mark.  Otherwise, we leave the pre-panic mbuf allocation alone.
In a future patch in this series, this will allow initiating netdump from
panic ddb(4) without pre-panic configuration.

No other functional change intended.

Reviewed by:	markj (earlier version)
Some discussion with:	emaste, jhb
Objection from:	marius
Differential Revision:	https://reviews.freebsd.org/D21421
2019-10-17 16:23:03 +00:00
..
2019-05-24 06:07:33 +00:00
2018-07-07 15:55:52 +00:00
2019-02-25 21:59:01 +00:00
2019-05-28 18:05:10 +00:00
2019-03-19 14:34:53 +00:00
2019-09-28 22:23:21 +00:00
2019-05-30 13:52:32 +00:00
2019-10-07 22:40:05 +00:00
2019-10-13 22:26:55 +00:00
2019-10-07 22:40:05 +00:00
2019-09-23 14:34:23 +00:00
2019-10-14 20:23:16 +00:00
2018-08-21 10:08:12 +00:00
2019-05-23 12:51:13 +00:00
2019-10-14 20:18:36 +00:00
2019-10-16 14:42:49 +00:00
2019-07-10 12:40:07 +00:00
2019-09-24 16:49:42 +00:00
2019-02-05 21:37:34 +00:00
2019-10-15 18:58:01 +00:00
2019-03-11 14:26:45 +00:00
2018-04-13 20:30:49 +00:00
2019-02-05 21:37:34 +00:00
2018-09-26 19:41:00 +00:00
2019-06-08 16:26:56 +00:00
2019-02-05 21:37:34 +00:00
2018-07-27 10:40:48 +00:00
2019-10-17 14:58:03 +00:00
2019-02-04 21:28:25 +00:00
2019-04-16 02:46:21 +00:00
2019-09-30 15:59:07 +00:00
2019-08-30 00:40:08 +00:00
2019-02-26 19:55:03 +00:00