If we think of the context of ODP applications in the field, not on
developer machines:
The system will be dimensioned to support whatever memory is required for
the different components, including ODP.
So it is just about doing the proper reservations, not asking what is
available. the
On Mon, Oct 23, 2017 at 2:22 PM, Maxim Uvarov
wrote:
> On 10/23/17 18:23, Francois Ozog wrote:
> > Hi Maxim,
> >
> > Is this regular memory or DMA capable memory?
> >
> > This would mean application would know how, for instance, to handle
> things
> > when memory is
On 10/23/17 18:23, Francois Ozog wrote:
> Hi Maxim,
>
> Is this regular memory or DMA capable memory?
>
> This would mean application would know how, for instance, to handle things
> when memory is lower than a threshold or something similar; or it may
> decide to use a percentage of memory for
Hi Maxim,
Is this regular memory or DMA capable memory?
This would mean application would know how, for instance, to handle things
when memory is lower than a threshold or something similar; or it may
decide to use a percentage of memory for packet pools; or many other
policies. I don't see
Applications should request the amount of storage they need (possibly as
configured) rather than trying to grab everything they can find "just in
case". Especially in an NFV environment that's not very neighborly behavior.
On Mon, Oct 23, 2017 at 2:44 AM, Dmitry Eremin-Solenikov <
On 23/10/17 10:39, Maxim Uvarov wrote:
> It might be reasonable to add also api call to get return free memory. So
> that application can adjust pools /buffers size according to hardware or VM
> settings. Which might be good fit for NFV set up.
> Any opinions on that?
It would depend on the
It might be reasonable to add also api call to get return free memory. So
that application can adjust pools /buffers size according to hardware or VM
settings. Which might be good fit for NFV set up.
Any opinions on that?
Maxim.