From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Yuval Shaia <yuval.shaia@oracle.com>,
Anthony Perard <anthony.perard@citrix.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 4/5] pvrdma: initial implementation
Date: Wed, 20 Dec 2017 06:08:59 +0200 [thread overview]
Message-ID: <20171220060700-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAAdtpL5XgR5wvJzfLHdtdR00fm9VPU50yycG-pdeL4i8-9Hsmw@mail.gmail.com>
On Tue, Dec 19, 2017 at 04:13:18PM -0300, Philippe Mathieu-Daudé wrote:
> Hi Marcel, Yuval,
>
> On Sun, Dec 17, 2017 at 9:54 AM, Marcel Apfelbaum <marcel@redhat.com> wrote:
> > From: Yuval Shaia <yuval.shaia@oracle.com>
> >
> > PVRDMA is the QEMU implementation of VMware's paravirtualized RDMA device.
> > It works with its Linux Kernel driver AS IS, no need for any special guest
> > modifications.
> >
> > While it complies with the VMware device, it can also communicate with bare
> > metal RDMA-enabled machines and does not require an RDMA HCA in the host, it
> > can work with Soft-RoCE (rxe).
> >
> > It does not require the whole guest RAM to be pinned allowing memory
> > over-commit and, even if not implemented yet, migration support will be
> > possible with some HW assistance.
> >
> > Signed-off-by: Yuval Shaia <yuval.shaia@oracle.com>
> > Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
> > ---
> [...]
> > 28 files changed, 5132 insertions(+), 4 deletions(-)
> > create mode 100644 hw/net/pvrdma/pvrdma.h
> > create mode 100644 hw/net/pvrdma/pvrdma_backend.c
> > create mode 100644 hw/net/pvrdma/pvrdma_backend.h
> > create mode 100644 hw/net/pvrdma/pvrdma_backend_defs.h
> > create mode 100644 hw/net/pvrdma/pvrdma_cmd.c
> > create mode 100644 hw/net/pvrdma/pvrdma_defs.h
> > create mode 100644 hw/net/pvrdma/pvrdma_dev_api.h
> > create mode 100644 hw/net/pvrdma/pvrdma_dev_ring.c
> > create mode 100644 hw/net/pvrdma/pvrdma_dev_ring.h
> > create mode 100644 hw/net/pvrdma/pvrdma_ib_verbs.h
> > create mode 100644 hw/net/pvrdma/pvrdma_main.c
> > create mode 100644 hw/net/pvrdma/pvrdma_qp_ops.c
> > create mode 100644 hw/net/pvrdma/pvrdma_qp_ops.h
> > create mode 100644 hw/net/pvrdma/pvrdma_ring.h
> > create mode 100644 hw/net/pvrdma/pvrdma_rm.c
> > create mode 100644 hw/net/pvrdma/pvrdma_rm.h
> > create mode 100644 hw/net/pvrdma/pvrdma_rm_defs.h
> > create mode 100644 hw/net/pvrdma/pvrdma_types.h
> > create mode 100644 hw/net/pvrdma/pvrdma_utils.c
> > create mode 100644 hw/net/pvrdma/pvrdma_utils.h
> > create mode 100644 hw/net/pvrdma/trace-events
> [...]
>
> Since we already have a hw/xenpv/ directory,
But e.g. xen nic is under hw/net/
> can we place these files
> into hw/vmwarepv/ rather than hw/net/pvrdma/?
>
> A smarter move might be to create a hw/pv/ dir and have hw/pv/{xen,vmware}.
>
> Regards,
>
> Phil.
That's not how we layout things. We group them by function not by
interface. Thus I think that hw/rdma/ is better.
--
MST
next prev parent reply other threads:[~2017-12-20 4:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 12:54 [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation Marcel Apfelbaum
2017-12-17 12:54 ` [Qemu-devel] [PATCH V2 1/5] pci/shpc: Move function to generic header file Marcel Apfelbaum
2017-12-17 18:16 ` Philippe Mathieu-Daudé
2017-12-17 19:03 ` Yuval Shaia
2017-12-17 12:54 ` [Qemu-devel] [PATCH V2 2/5] mem: add share parameter to memory-backend-ram Marcel Apfelbaum
2017-12-17 12:54 ` [Qemu-devel] [PATCH V2 3/5] docs: add pvrdma device documentation Marcel Apfelbaum
2017-12-19 17:47 ` Michael S. Tsirkin
2017-12-20 14:45 ` Marcel Apfelbaum
2017-12-17 12:54 ` [Qemu-devel] [PATCH V2 4/5] pvrdma: initial implementation Marcel Apfelbaum
2017-12-19 16:12 ` Michael S. Tsirkin
2017-12-19 17:29 ` Marcel Apfelbaum
2017-12-19 17:48 ` Michael S. Tsirkin
2017-12-20 15:25 ` Yuval Shaia
2017-12-20 18:01 ` Michael S. Tsirkin
2017-12-19 19:13 ` Philippe Mathieu-Daudé
2017-12-20 4:08 ` Michael S. Tsirkin [this message]
2017-12-20 14:46 ` Marcel Apfelbaum
2017-12-17 12:54 ` [Qemu-devel] [PATCH V2 5/5] MAINTAINERS: add entry for hw/net/pvrdma Marcel Apfelbaum
2017-12-19 17:49 ` Michael S. Tsirkin
2017-12-19 18:05 ` [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation Michael S. Tsirkin
2017-12-20 15:07 ` Marcel Apfelbaum
2017-12-21 0:05 ` Michael S. Tsirkin
2017-12-21 7:27 ` Yuval Shaia
2017-12-21 14:22 ` Michael S. Tsirkin
2017-12-21 15:59 ` Marcel Apfelbaum
2017-12-21 20:46 ` Michael S. Tsirkin
2017-12-21 22:30 ` Yuval Shaia
2017-12-22 4:58 ` Marcel Apfelbaum
2017-12-20 17:56 ` Yuval Shaia
2017-12-20 18:05 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171220060700-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=yuval.shaia@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).