dbbbad23e3
VF will build two queues (csq: command send queue, crq: command receive queue) with firmware, the crq may contain the following messages: 1) mailbox response message which was the ack of mailbox sync request. 2) PF's link status change message which may send by PF at anytime; Currently, any threads in the primary and secondary processes could send mailbox sync request, so it will need to process the crq messages in there own thread context. If the crq hold two messages: a) PF's link status change message, b) mailbox response message when secondary process deals with the crq messages, it will lead to report lsc event in secondary process because it uses the policy of processing all pending messages at once. We use the following scheme to solve it: 1) threads in secondary process could only process specifics messages (eg. mailbox response message) in crq, if the message processed, its opcode will rewrite with zero, then the intr thread in primary process will not process again. 2) threads other than intr thread in the primary process use the same processing logic as the threads in secondary process. 3) intr thread in the primary process could process all messages. Fixes: |
||
|---|---|---|
| .ci | ||
| .github/workflows | ||
| app | ||
| buildtools | ||
| config | ||
| devtools | ||
| doc | ||
| drivers | ||
| examples | ||
| kernel | ||
| lib | ||
| license | ||
| usertools | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| ABI_VERSION | ||
| MAINTAINERS | ||
| Makefile | ||
| meson_options.txt | ||
| meson.build | ||
| README | ||
| VERSION | ||
DPDK is a set of libraries and drivers for fast packet processing. It supports many processor architectures and both FreeBSD and Linux. The DPDK uses the Open Source BSD-3-Clause license for the core libraries and drivers. The kernel components are GPL-2.0 licensed. Please check the doc directory for release notes, API documentation, and sample application information. For questions and usage discussions, subscribe to: users@dpdk.org Report bugs and issues to the development mailing list: dev@dpdk.org