Re: [dpdk-dev] [RFC 0/2] CPU non-blocking delay

2018-09-03 Thread Ilya Maximets
On 31.08.2018 16:39, Bruce Richardson wrote: > On Fri, Aug 31, 2018 at 03:45:15PM +0300, Ilya Maximets wrote: >> Sending as RFC because I failed to force meson to >> build without deprecation warnings. I tried a lot >> of different combinations of 'allow_experimental_apis' >> and '-DALLOW_EXPERIMEN

Re: [dpdk-dev] [RFC 0/2] CPU non-blocking delay

2018-08-31 Thread Bruce Richardson
On Fri, Aug 31, 2018 at 03:45:15PM +0300, Ilya Maximets wrote: > Sending as RFC because I failed to force meson to > build without deprecation warnings. I tried a lot > of different combinations of 'allow_experimental_apis' > and '-DALLOW_EXPERIMENTAL_APIS' without success. > Any help appreciated.

Re: [dpdk-dev] [RFC 0/2] CPU non-blocking delay

2018-08-31 Thread Bruce Richardson
On Fri, Aug 31, 2018 at 03:45:15PM +0300, Ilya Maximets wrote: > Sending as RFC because I failed to force meson to > build without deprecation warnings. I tried a lot > of different combinations of 'allow_experimental_apis' > and '-DALLOW_EXPERIMENTAL_APIS' without success. > Any help appreciated.

[dpdk-dev] [RFC 0/2] CPU non-blocking delay

2018-08-31 Thread Ilya Maximets
Sending as RFC because I failed to force meson to build without deprecation warnings. I tried a lot of different combinations of 'allow_experimental_apis' and '-DALLOW_EXPERIMENTAL_APIS' without success. Any help appreciated. Ilya Maximets (2): eal: add nanosleep based delay function drivers/n