[dpdk-dev] [PATCH v2 1/4] lib: introduce IF Proxy library

Andrzej Ostruszka [C] aostruszka at marvell.com
Thu Jul 9 10:43:32 CEST 2020


First of all let me thank you all one again for the time you took 
looking at this and summarize your feedback as I understand it.

1. Don't use interrupt thread because in heavy load scenarios this might 
cause problems.
2. Provide higher level functionality - so that application can just use 
it instead of maintaining the info on their own.
3. Provide way to have control over the changes - if I remember 
correctly someone wanted apps to be able to reject the changes (meaning 
rolling back the changes to the kernel)
4. Don't parse netlink on your own (use e.g. libmnl)
5. Don't use callbacks

These are the specific things that I managed to understand.  Have I 
missed anything?  If so please add this to the list!

To that I say:
Ad1. Agree, will change that.
Ad2. OK, but this can be added later.
Ad3. Currently the lib was meant to be one way but as in previous point 
this can change in the future.
Ad4. As mentioned in previous mail I judged it not worthy of adding 
dependency but I'm OK with using it.  This might be more relevant when 
we address point 3 and can be introduced then, but I can do it now.
Ad5. There are now notification queues and I'm fine with adapting to any 
standard of notification/communication that DPDK will agree on.

In addition may I ask your opinion on the changes that are required 
before the library can be accepted?

Thank you in advance
With regards
Andrzej Ostruszka



More information about the dev mailing list