Re: [dpdk-dev] [PATCH] vhost: add API for getting last_idx of vrings

2018-07-26 Thread Stojaczyk, DariuszX
aszX > > Cc: dev@dpdk.org; y...@fridaylinux.org; Verkamp, Daniel > ; Harris, James R ; > Wodkowski, PawelX ; Stojaczyk, DariuszX > > Subject: Re: [dpdk-dev] [PATCH] vhost: add API for getting last_idx of vrings > > What is the status of this patch? > > 19/04/

Re: [dpdk-dev] [PATCH] memory: fix alignment in eal_get_virtual_area()

2018-07-17 Thread Stojaczyk, DariuszX
> -Original Message- > From: Burakov, Anatoly > Sent: Monday, July 16, 2018 4:17 PM > To: Stojaczyk, DariuszX ; dev@dpdk.org > Cc: sta...@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] memory: fix alignment in > eal_get_virtual_area() > > On 16-Jul-18 3:01

Re: [dpdk-dev] [PATCH] mem: fix alignment of requested virtual areas

2018-07-17 Thread Stojaczyk, DariuszX
> -Original Message- > From: Burakov, Anatoly > Sent: Monday, July 16, 2018 4:57 PM > To: dev@dpdk.org > Cc: tho...@monjalon.net; Yao, Lei A ; Stojaczyk, DariuszX > ; sta...@dpdk.org > Subject: [PATCH] mem: fix alignment of requested virtual areas > > The

Re: [dpdk-dev] [PATCH] memory: fix alignment in eal_get_virtual_area()

2018-07-16 Thread Stojaczyk, DariuszX
> -Original Message- > From: Burakov, Anatoly > Sent: Monday, July 16, 2018 2:58 PM > To: Stojaczyk, DariuszX ; dev@dpdk.org > Cc: sta...@dpdk.org > Subject: Re: [PATCH] memory: fix alignment in eal_get_virtual_area() > > On 13-Jun-18 8:08 PM, Dariusz Stojaczyk

Re: [dpdk-dev] [RFC v3 0/7] vhost2: new librte_vhost2 proposal

2018-06-26 Thread Stojaczyk, DariuszX
> -Original Message- > From: Bie, Tiwei > Sent: Tuesday, June 26, 2018 10:22 AM > To: Stojaczyk, DariuszX > Cc: Dariusz Stojaczyk ; dev@dpdk.org; Maxime > Coquelin ; Tetsuya Mukawa > ; Stefan Hajnoczi ; Thomas > Monjalon ; y...@fridaylinux.org; Harris, Jame

Re: [dpdk-dev] [PATCH 1/2] eal/thread: fix return codes for rte_thread_setname()

2018-06-25 Thread Stojaczyk, DariuszX
> -Original Message- > From: Olivier Matz [mailto:olivier.m...@6wind.com] > Sent: Monday, June 25, 2018 4:36 PM > To: Burakov, Anatoly > Cc: Stojaczyk, DariuszX ; dev@dpdk.org; > thomas.monja...@6wind.com; sta...@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 1/2] e

Re: [dpdk-dev] [RFC v3 0/7] vhost2: new librte_vhost2 proposal

2018-06-25 Thread Stojaczyk, DariuszX
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Tiwei Bie > Sent: Monday, June 25, 2018 1:02 PM > > > Hi Dariusz, > Hi Tiwei, > Thank you for putting efforts in making the DPDK > vhost more generic! > > From my understanding, your proposal is that: > > 1

Re: [dpdk-dev] [PATCH] memory: do not use base-virtaddr in secondary processes

2018-06-18 Thread Stojaczyk, DariuszX
> -Original Message- > From: Alejandro Lucero [mailto:alejandro.luc...@netronome.com] > Sent: Monday, June 18, 2018 9:33 PM > > On Mon, Jun 18, 2018 at 8:03 PM, Stojaczyk, DariuszX > mailto:dariuszx.stojac...@intel.com> > > wrote: > > Can you poi

Re: [dpdk-dev] [PATCH] memory: do not use base-virtaddr in secondary processes

2018-06-18 Thread Stojaczyk, DariuszX
> -Original Message- > From: Alejandro Lucero [mailto:alejandro.luc...@netronome.com] > Sent: Monday, June 18, 2018 7:22 PM > > Should not be better to handle these allocations being aware about the > problem for secondary processes? > > I do not know exactly what are the (other) reasons

Re: [dpdk-dev] [PATCH 1/2] eal/thread: fix return codes for rte_thread_setname()

2018-06-08 Thread Stojaczyk, DariuszX
+CC tho...@monjalon.net The previous @6wind email appears to be unavailable now. > -Original Message- > From: Stojaczyk, DariuszX > Sent: Friday, June 8, 2018 2:37 PM > To: dev@dpdk.org > Cc: Stojaczyk, DariuszX ; > thomas.monja...@6wind.com; sta...@dpdk.org > Sub

Re: [dpdk-dev] [PATCH 2/2] memalloc: keep in mind a failed MAP_FIXED mmap may still perform an unmap

2018-06-01 Thread Stojaczyk, DariuszX
> -Original Message- > From: Burakov, Anatoly > Sent: Friday, June 1, 2018 1:09 PM > To: Stojaczyk, DariuszX ; dev@dpdk.org > Subject: Re: [PATCH 2/2] memalloc: keep in mind a failed MAP_FIXED > mmap may still perform an unmap > > On 01-Jun-18 1:51 PM, Dariusz S

Re: [dpdk-dev] [PATCH 1/2] memalloc: do not leave unmapped holes in EAL virtual memory area

2018-06-01 Thread Stojaczyk, DariuszX
> -Original Message- > From: Burakov, Anatoly > Sent: Friday, June 1, 2018 1:00 PM > On 01-Jun-18 1:51 PM, Dariusz Stojaczyk wrote: > > EAL reserves a huge area in virtual address space to provide virtual > > address contiguity for e.g. > > future memory extensions (memory hotplug). During

Re: [dpdk-dev] [PATCH v2 1/2] memalloc: do not leave unmapped holes in EAL virtual memory area

2018-06-01 Thread Stojaczyk, DariuszX
The Intel SMTP server keeps dying to me. It's really not fun trying to resend these messages for half an hour without success. I'll resend this series from my private mail in the evening. D. > -Original Message- > From: Stojaczyk, DariuszX > Sent: Friday, June 1, 201

Re: [dpdk-dev] [RFC v2] vhost: new rte_vhost API proposal

2018-05-30 Thread Stojaczyk, DariuszX
> -Original Message- > From: Stefan Hajnoczi [mailto:stefa...@redhat.com] > Sent: Wednesday, May 30, 2018 10:57 AM > On Tue, May 29, 2018 at 01:38:33PM +0000, Stojaczyk, DariuszX wrote: > > > > > > > -Original Message- > > > From: S

Re: [dpdk-dev] [RFC v2] vhost: new rte_vhost API proposal

2018-05-29 Thread Stojaczyk, DariuszX
> -Original Message- > From: Stefan Hajnoczi [mailto:stefa...@redhat.com] > Sent: Friday, May 25, 2018 12:06 PM > On Fri, May 18, 2018 at 03:01:05PM +0200, Dariusz Stojaczyk wrote: > > +struct rte_vhost2_msg { > > + uint32_t id; > > Is this what the vhost-user specification calls the

Re: [dpdk-dev] [RFC v2] vhost: new rte_vhost API proposal

2018-05-22 Thread Stojaczyk, DariuszX
Hi Maxime, > -Original Message- > From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] > Sent: Friday, May 18, 2018 9:51 PM > On 05/18/2018 03:01 PM, Dariusz Stojaczyk wrote: > > rte_vhost is not vhost-user spec compliant. Some Vhost drivers have > > been already confirmed not to work

Re: [dpdk-dev] [RFC] vhost: new rte_vhost API proposal

2018-05-18 Thread Stojaczyk, DariuszX
> -Original Message- > From: Stefan Hajnoczi [mailto:stefa...@redhat.com] > Sent: Friday, May 11, 2018 6:06 PM > On Fri, May 11, 2018 at 05:55:45AM +0000, Stojaczyk, DariuszX wrote: > > > -Original Message- > > > From: Stefan Hajnoczi [mailto:s

Re: [dpdk-dev] [RFC] vhost: new rte_vhost API proposal

2018-05-10 Thread Stojaczyk, DariuszX
Hi, > -Original Message- > From: Stefan Hajnoczi [mailto:stefa...@redhat.com] > Sent: Friday, May 11, 2018 12:37 AM > On Thu, May 10, 2018 at 03:22:53PM +0200, Dariusz Stojaczyk wrote: > > rte_virtio would offer both vhost and virtio driver APIs. These two > > have a lot of common code for

Re: [dpdk-dev] virtio with 2MB hugepages - bringing back single file segments

2018-03-02 Thread Stojaczyk, DariuszX
Hi Maxime, > > Hi, > > > > I'm trying to make a vhost-user initiator built upon DPDK work with > > 2MB hugepages. In the initiator we have to share all memory with the host > process, so it can perform DMA. DPDK currently enforces having one descriptor > per hugepage and there's an artificial limi

[dpdk-dev] virtio with 2MB hugepages - bringing back single file segments

2018-03-01 Thread Stojaczyk, DariuszX
Hi, I'm trying to make a vhost-user initiator built upon DPDK work with 2MB hugepages. In the initiator we have to share all memory with the host process, so it can perform DMA. DPDK currently enforces having one descriptor per hugepage and there's an artificial limit of shared descriptors in D

Re: [dpdk-dev] [PATCH v2] vhost: added user callbacks for socket open/close

2017-08-28 Thread Stojaczyk, DariuszX
Hi Jens, > I'm still not sure I understand the use case. So just for my > understanding: users need to distinct between "the device is going away > temporarily, keep the connection" and "we're shutting down for good", is > that it? Yes, exactly. > Maybe it's just me or maybe it means you could e

Re: [dpdk-dev] [PATCH] vhost: added user callbacks for socket open/close

2017-08-22 Thread Stojaczyk, DariuszX
Hi Jens, > I'm a little uncertain but my gut feeling is that in this context a > connection is > something between two sockets, not between devices. What do you mean? This is a unix domain socket connection. DPDK can create the socket, then the client may connect to it via connect(2). > I woul

Re: [dpdk-dev] [PATCH v3 3/3] vhost: access VhostUsrMsg via packed struct

2017-05-24 Thread Stojaczyk, DariuszX
> This is for fixing compile warnings with new clang 4.0? > > http://dpdk.org/ml/archives/dev/2017-April/064089.html > > If so, please show the exact warning in the commit log. > Everything compiles, but is undefined behavior. Accessing packed struct's fields through pointers would have t

Re: [dpdk-dev] [PATCH] vhost: fix deadlock on rte_vhost_driver_unregister()

2017-05-16 Thread Stojaczyk, DariuszX
> -Original Message- > From: Stojaczyk, DariuszX > Sent: Tuesday, May 16, 2017 4:35 PM > To: dev@dpdk.org > Cc: Wodkowski, PawelX ; Stojaczyk, DariuszX > > Subject: [PATCH] vhost: fix deadlock on rte_vhost_driver_unregister() > > Consider the following scen

Re: [dpdk-dev] [PATCH v2 1/3] vhost: fix malloc in rte_vhost_get_mem_table

2017-05-11 Thread Stojaczyk, DariuszX
The size variable is still used a few lines later: memcpy(m->regions, dev->mem->regions, size); That line is ok. Only the amount of malloc'ed memory was too small. -Original Message- From: Jens Freimann [mailto:jfrei...@redhat.com] Sent: Thursday, May 11, 2017 1:42 PM