On 25.01.2019 21:56, Ben Pfaff wrote:
> On Fri, Jan 25, 2019 at 04:08:10PM +0300, Ilya Maximets wrote:
>> On 23.01.2019 15:40, Aaron Conole wrote:
>>> Ilya Maximets writes:
>>>
Aaron, what do you think about supporting tags like 'Based-on' in ovsrobot
?
For example, patchew in
On Fri, Jan 25, 2019 at 04:08:10PM +0300, Ilya Maximets wrote:
> On 23.01.2019 15:40, Aaron Conole wrote:
> > Ilya Maximets writes:
> >
> >> Aaron, what do you think about supporting tags like 'Based-on' in ovsrobot
> >> ?
> >> For example, patchew in QEMU parses 'Based-on: ' tags.
> >> Maybe
On 23.01.2019 15:40, Aaron Conole wrote:
> Ilya Maximets writes:
>
>> Aaron, what do you think about supporting tags like 'Based-on' in ovsrobot ?
>> For example, patchew in QEMU parses 'Based-on: ' tags.
>> Maybe we can use patchwork ids or something similar.
>
> I think there's a way to do it
Ilya Maximets writes:
> Aaron, what do you think about supporting tags like 'Based-on' in ovsrobot ?
> For example, patchew in QEMU parses 'Based-on: ' tags.
> Maybe we can use patchwork ids or something similar.
I think there's a way to do it without a tag in the commit message. I
don't like
Since 18.05 release, DPDK moved to dynamic memory model in which
hugepages could be allocated on demand. At the same time '--socket-mem'
option was re-defined as a size of pre-allocated memory, i.e. memory
that should be allocated at startup and could not be freed.
So, DPDK with a new memory model
