FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-12-03T08:30:29Z 2020-12-03T08:30:29Z Navdeep Parhar np@FreeBSD.org 2020-12-03T08:30:29Z urn:sha1:8eba75ed68854188c01a2058fe1f826b3428dbfa It is common for freelists to be starving when a netmap application stops. Mailbox commands to free queues can hang in such a situation. Avoid that by not freeing the queues when netmap is switched off. Instead, use an alternate method to stop the queues without releasing the context ids. If netmap is enabled again later then the same queue is reinitialized for use. Move alloc_nm_rxq and txq to t4_netmap.c while here. MFC after: 1 week Sponsored by: Chelsio Communications 2020-12-02T20:54:03Z Navdeep Parhar np@FreeBSD.org 2020-12-02T20:54:03Z urn:sha1:f42f3b2955e5afa770275fd76b4f754fbd67bbeb r367917 fixed the backpressure on the netmap rxq being stopped but that doesn't help if some other netmap rxq is starved (because it is stopping too although the driver doesn't know this yet) and blocks the pipeline. An alternate fix that works in all cases will be checked in instead. Sponsored by: Chelsio Communications 2020-11-21T03:27:32Z Navdeep Parhar np@FreeBSD.org 2020-11-21T03:27:32Z urn:sha1:b3718e2d7ebfe7fc0bb57bd0906aacc28dd755b2 The netmap application using the driver is responsible for replenishing the receive freelists and they may be totally depleted when the application exits. Packets in flight, if any, might block the pipeline in case there aren't enough buffers left in the freelist. Avoid this by filling up the freelists with a driver allocated buffer. MFC after: 1 week Sponsored by: Chelsio Communications 2020-10-22T08:40:25Z Navdeep Parhar np@FreeBSD.org 2020-10-22T08:40:25Z urn:sha1:b20b25e744778ac54d54f5486035e70d6570f4d9 The firmware can allocate ingress and egress context ids anywhere from its configured range. Size the iq/eq maps to match the entire range instead of assuming that the firmware always allocates the first available context id. Reported by: Baptiste Wicht @ Verisign MFC after: 1 week Sponsored by: Chelsio Communications 2020-09-29T09:25:52Z Navdeep Parhar np@FreeBSD.org 2020-09-29T09:25:52Z urn:sha1:822967e7e5b24d5fa980f69cab7b2982e1b6fa42 Bind the netmap tx queues to a special '0xff' scheduling class which makes the firmware skip some processing related to rate limiting on the outgoing traffic. Future firmwares will do this automatically. MFC after: 1 week Sponsored by: Chelsio Communications 2020-09-29T09:11:51Z Navdeep Parhar np@FreeBSD.org 2020-09-29T09:11:51Z urn:sha1:7efe256233388e16d5b37c70e8ad0afc4b55fe4d 2020-09-29T07:51:06Z Navdeep Parhar np@FreeBSD.org 2020-09-29T07:51:06Z urn:sha1:15ca0766ed72ee8c2294cf047d2d391ffab2c016 maximum burst size used when fetching descriptors from the list. MFC after: 1 week Sponsored by: Chelsio Communications 2020-09-29T07:36:21Z Navdeep Parhar np@FreeBSD.org 2020-09-29T07:36:21Z urn:sha1:f7b8615af50435a43b9a74acb0d842283765a4a4 the interface is down. MFC after: 1 week 2020-09-29T05:08:45Z Navdeep Parhar np@FreeBSD.org 2020-09-29T05:08:45Z urn:sha1:a9f476580eb05efc1637bf7c9eb9602e1592d50f - Only active netmap receive queues should be in the RSS lookup table. - The RSS table should be restored for NIC operation when the last active netmap queue is switched off, not the first one. - Support repeated netmap ON/OFF on a subset of the queues. This works whether the the queues being enabled and disabled are the only ones active or not. Some kring indexes have to be reset in the driver for the second case. MFC after: 1 week Sponsored by: Chelsio Communications 2020-06-25T17:04:22Z Navdeep Parhar np@FreeBSD.org 2020-06-25T17:04:22Z urn:sha1:7c228be30bd14fd8b683426bc91a608827426abf There were quite a few places where port_info was being accessed only to get to the adapter. Reviewed by: jhb@ MFC after: 1 week Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D25432