13627105546 commented on issue #16859: URL: https://github.com/apache/nuttx/issues/16859#issuecomment-3194444873
At present, we do not have direct example code, but I can explain the interface concept provided to the driver: When the socket detects a change in the CPU ID where the application is located, it needs to call the driver interface, pass the hash value and the latest CPU ID to the driver, and update the hardware flow table Hash calculation needs to be based on the protocol type of the message. If there are four tuples (SIP, SPORT, DIP, DPORT), use them to calculate the hash value. Otherwise, use two tuples (SIP, DIP, such as ARP messages) to calculate the hash value, and the algorithm needs to be consistent with the hardware Give the driver an interface with quadruple input and output to obtain the CPU ID value -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org