RE: [PATCH v7] app/testpmd: monitor state of primary process when using secondary

["Varghese, Vipin" <Vipin.Varghese@amd.com>]

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

[Public]

Hi Khadem,

Please do not use `sorry for any confusion`. Very clearly, I shared what works and why your case is different.
Snipped

Hi Vipin,
sorry for any confusion. I am only trying to explain that these patches are in its final state (waiting to upstream).

[VV] it is not about the state, but of the quality and state.

You have provided your valuable insights and
I am very thankful for that. There was much discussion about these patches from start to finish.

Already mentioned that with Stephen and other community members, the discussion was started earlier and I have provided all the information
to you in a singla email.
 "First we tried
to prevent the crashes at PMD level, but it was not possible to
add checks in each PMD. Then we tried to add safety checks
in the ethdev layer, and it was not suitable as with primary closing
all reference to device information (pointers) would lead to crashes."
[VV] I did also share I checked these eemails, none of them discussed use for multi process communication as a trigger or why it is not useful.
@Stephen Hemminger<mailto:stephen@networkplumber.org>  agreed to add a primary-secondary monitoring mechanism.

I am always open to healthy conversation!

I will rest it here, I clearly understand your previous content ` The community agrees with the current solution. `

[-- Attachment #2: Type: text/html, Size: 5294 bytes --]