Re: [dpdk-dev] [RFC] net/virtio-user: avoid parsing process mappings

On 28-Aug-18 9:42 AM, Tiwei Bie wrote: On Tue, Aug 28, 2018 at 09:12:38AM +0100, Burakov, Anatoly wrote: On 28-Aug-18 8:53 AM, Tiwei Bie wrote: [...] - for (i = 0; i < num; ++i) { - mr = &msg->payload.memory.regions[i]; - mr->guest_phys_addr = huges[i].addr; /*

Re: [dpdk-dev] [RFC] net/virtio-user: avoid parsing process mappings

On Tue, Aug 28, 2018 at 09:12:38AM +0100, Burakov, Anatoly wrote: > On 28-Aug-18 8:53 AM, Tiwei Bie wrote: [...] > > > > - for (i = 0; i < num; ++i) { > > - mr = &msg->payload.memory.regions[i]; > > - mr->guest_phys_addr = huges[i].addr; /* use vaddr! */ > > - mr-

Re: [dpdk-dev] [RFC] net/virtio-user: avoid parsing process mappings

On 28-Aug-18 8:53 AM, Tiwei Bie wrote: Recently some memory APIs were introduced to allow users to get the file descriptors for each memory segments. We can leverage those APIs to get rid of the /proc magic on memory table preparation in vhost-user backend. Signed-off-by: Tiwei Bie --- This pat

[dpdk-dev] [RFC] net/virtio-user: avoid parsing process mappings

Recently some memory APIs were introduced to allow users to get the file descriptors for each memory segments. We can leverage those APIs to get rid of the /proc magic on memory table preparation in vhost-user backend. Signed-off-by: Tiwei Bie --- This patch depends on below patch set: https://pa