Re: [ovs-dev] [PATCH v1] dpdk: Use --in-memory by default.

2021-12-06 Thread Ilya Maximets
On 12/6/21 02:49, Mike Pattrick wrote: > On Fri, Dec 3, 2021 at 8:15 PM Ilya Maximets wrote: >> >> On 11/30/21 22:31, Mike Pattrick wrote: >>> If anonymous memory mapping is supported by the kernel, it's better >>> to run OVS entirely in memory rather than creating shared data >>> structures. OVS

Re: [ovs-dev] [PATCH v1] dpdk: Use --in-memory by default.

2021-12-05 Thread Mike Pattrick
On Fri, Dec 3, 2021 at 8:15 PM Ilya Maximets wrote: > > On 11/30/21 22:31, Mike Pattrick wrote: > > If anonymous memory mapping is supported by the kernel, it's better > > to run OVS entirely in memory rather than creating shared data > > structures. OVS doesn't work in multi-process mode, so

Re: [ovs-dev] [PATCH v1] dpdk: Use --in-memory by default.

2021-12-03 Thread Ilya Maximets
On 11/30/21 22:31, Mike Pattrick wrote: > If anonymous memory mapping is supported by the kernel, it's better > to run OVS entirely in memory rather than creating shared data > structures. OVS doesn't work in multi-process mode, so there is no need > to litter a filesystem and experience random

Re: [ovs-dev] [PATCH v1] dpdk: Use --in-memory by default.

2021-11-30 Thread 0-day Robot
Bleep bloop. Greetings Mike Pattrick, I am a robot and I have tried out your patch. Thanks for your contribution. I encountered some error that I wasn't expecting. See the details below. checkpatch: WARNING: Unexpected sign-offs from developers who are not authors or co-authors or

[ovs-dev] [PATCH v1] dpdk: Use --in-memory by default.

2021-11-30 Thread Mike Pattrick
If anonymous memory mapping is supported by the kernel, it's better to run OVS entirely in memory rather than creating shared data structures. OVS doesn't work in multi-process mode, so there is no need to litter a filesystem and experience random crashes due to old memory chunks stored in