On 08-Feb-20 8:09 PM, Dmitry Kozlyuk wrote:
The main reason DPDK memory management works the way it does is because
of need to support multiprocess. In order to map memory in all
processes, we need that space reserved (otherwise there's no guarantee
that the newly mapped memory segment will be ma
> The main reason DPDK memory management works the way it does is because
> of need to support multiprocess. In order to map memory in all
> processes, we need that space reserved (otherwise there's no guarantee
> that the newly mapped memory segment will be mapped in all processes,
> and it'll
02/02/2020 21:37, Dmitry Kozliuk:
> Where do I find a high-level plan of comprehensive Windows support: design
> decisions, implementation order, etc?
Please help documenting design decisions in the DPDK doc.
For implementation order, we'll discuss it soon together.
> Information on the subject i
On 02-Feb-20 8:37 PM, Dmitry Kozliuk wrote:
Hi everyone!
Hi,
Primary topics to discuss:
1. Memory management (@Anatoly)
1.1. MM changed radically since v18.08 and dpdk-next-windows does not
implement it properly anyway, it allocates segment lists in a PCI bus
driver.
Hi everyone!
Where do I find a high-level plan of comprehensive Windows support: design
decisions, implementation order, etc?
Information on the subject is very scarce, one may think it is abandoned.
Googling for "site:dpdk.org/ml/archives/dev/ windows" yields only two pages
of disjoint messages.
5 matches
Mail list logo
