Morten First of all thank you for your feedback. If anything else pops into your mind please do not hesitate to share it.
We just had a quick internal discussion and we decided that we'll try to come up with both options (callback and message queue). On 1/16/20 11:58 AM, Morten Brørup wrote: >> -----Original Message----- >> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Andrzej Ostruszka >> Sent: Thursday, January 16, 2020 11:43 AM [...] >> You'd still need to repack the message and that could be the job of the >> callback. >> >> At the moment we don't have much experience with the library and to me >> the callback is more generic approach with which one can achieve >> different designs. However nothing here is curved in stone so if we >> figure out that this is too generic we will change it. >> > > Please re-read my reply to Jerin Jacob why I prefer a pull model instead: > https://mails.dpdk.org/archives/dev/2020-January/155386.html Yes - I got your point first time. Remark above was not meant to imply that "pull mode" is not a valid way (it is perfectly valid and probably most often used in DPDK). I just noted that by staying at callback level only one can still implement it. But it is true that this way would impose more burden on the application writer - so instead we now plan to provide both options. > Take a stab at the example application, and see which design pattern is the > best fit. We will. This is a definitely a good idea to work out things in "battle". With regards Andrzej Ostruszka
