MFC: r345888: Use IN_foo() macros from sys/netinet/in.h inplace ofhandcrafted codeThere are a few places that use hand crafted versions of the macrosfrom sys/netinet/in.h making it difficult to a
MFC: r345888: Use IN_foo() macros from sys/netinet/in.h inplace ofhandcrafted codeThere are a few places that use hand crafted versions of the macrosfrom sys/netinet/in.h making it difficult to actually alter thevalues in use by these macros. Correct that by replacing handcraftedcode with proper macro usage.Reviewed by: karels, kristofApproved by: bde (mentor, implicit)Sponsored by: John GilmoreDifferential Revision: https://reviews.freebsd.org/D19317
show more ...
MFC r339883:Expose some netdump configuration parameters through sysctl.
UDP: further performance improvements on txCumulative throughput while running 64 netperf -H $DUT -t UDP_STREAM -- -m 1on a 2x8x2 SKL went from 1.1Mpps to 2.5MppsSingle stream throughput incre
UDP: further performance improvements on txCumulative throughput while running 64 netperf -H $DUT -t UDP_STREAM -- -m 1on a 2x8x2 SKL went from 1.1Mpps to 2.5MppsSingle stream throughput increases from 910kpps to 1.18MppsBaseline:https://people.freebsd.org/~mmacy/2018.05.11/udpsender2.svg- Protect read access to global ifnet list with epochhttps://people.freebsd.org/~mmacy/2018.05.11/udpsender3.svg- Protect short lived ifaddr references with epochhttps://people.freebsd.org/~mmacy/2018.05.11/udpsender4.svg- Convert if_afdata read lock path to epochhttps://people.freebsd.org/~mmacy/2018.05.11/udpsender5.svgA fix for the inpcbhash contention is pending sufficient timeon a canary at LLNW.Reviewed by: gallatinSponsored by: Limelight NetworksDifferential Revision: https://reviews.freebsd.org/D15409
Initialize the dumper struct before calling set_dumper().Fields owned by the generic code were being left uninitialized,causing problems in clear_dumper() if an error occurred.Coverity CID: 1391
Initialize the dumper struct before calling set_dumper().Fields owned by the generic code were being left uninitialized,causing problems in clear_dumper() if an error occurred.Coverity CID: 1391200X-MFC with: r333283
Fix netdump configuration when VIMAGE is enabled.We need to set the current vnet before iterating over the globalinterface list. Because the dump device may only be set from the host,only proceed
Fix netdump configuration when VIMAGE is enabled.We need to set the current vnet before iterating over the globalinterface list. Because the dump device may only be set from the host,only proceed with configuration if the thread belongs to the defaultvnet. [1]Also fix a resource leak that occurs if the priv_check() in set_dumper()fails.Reported by: mmacy, sbruno [1]Reviewed by: sbrunoX-MFC with: r333283Differential Revision: https://reviews.freebsd.org/D15449
Import the netdump client code.This is a component of a system which lets the kernel dump core toa remote host after a panic, rather than to a local storage device.The server component is availab
Import the netdump client code.This is a component of a system which lets the kernel dump core toa remote host after a panic, rather than to a local storage device.The server component is available in the ports tree. netdump isparticularly useful on diskless systems.The netdump(4) man page contains some details describing the protocol.Support for configuring netdump will be added to dumpon(8) in a futurecommit. To use netdump, the kernel must have been compiled with theNETDUMP option.The initial revision of netdump was written by Darrell Anderson andwas integrated into Sandvine's OS, from which this version was derived.Reviewed by: bdrewery, cem (earlier versions), julian, sbrunoMFC after: 1 monthX-MFC note: use a spare field in struct ifnetSponsored by: Dell EMC IsilonDifferential Revision: https://reviews.freebsd.org/D15253