On Thu, Nov 26, 2020 at 2:58 PM Reshma Pattan <[email protected]> wrote: > > Update the pdump library programmers guide and Howto doc > with the use of multi process channel replacing socket > based communication. > > Signed-off-by: Reshma Pattan <[email protected]> > Acked-by: Bruce Richardson <[email protected]>
[snip] > The library APIs ``rte_pdump_disable()`` and > ``rte_pdump_disable_by_deviceid()`` disables the packet capture. > -On each call to these APIs, the library creates a separate client socket, > creates the "pdump disable" request and sends > -the request to the server. The server that is listening on the socket will > take the request and disable the packet > -capture by removing the Ethernet RX and TX callbacks for the given port or > device_id and queue combinations. The server > -also sends the response back to the client about the status of the request > that was processed. After the response is > -received from the server, the client socket is closed. > +For the calls to these APIs from secondary process, the library creates the > "pdump disable" request and sends > +the request to the primary process over the multi process channel. The > primary process takes this request and disables the packet capture by > removing the Ethernet RX and TX callbacks for the given port or device_id and > queue combinations. I split this long line to multiple ~100 characters lines like the rest of the document. Applied, thanks. -- David Marchand
