From: Peter Xu <peterx@redhat.com>
To: Mattias Nissler <mnissler@rivosinc.com>
Cc: qemu-devel@nongnu.org, john.levon@nutanix.com,
stefanha@redhat.com,
"Richard Henderson" <richard.henderson@linaro.org>,
"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jagannathan Raman" <jag.raman@oracle.com>,
"David Hildenbrand" <david@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v4 1/5] softmmu: Per-AddressSpace bounce buffering
Date: Tue, 19 Sep 2023 13:12:25 -0400 [thread overview]
Message-ID: <ZQnWech0biGUuTHh@x1n> (raw)
In-Reply-To: <20230919160814.3343727-2-mnissler@rivosinc.com>
On Tue, Sep 19, 2023 at 09:08:09AM -0700, Mattias Nissler wrote:
> Instead of using a single global bounce buffer, give each AddressSpace
> its own bounce buffer. The MapClient callback mechanism moves to
> AddressSpace accordingly.
>
> This is in preparation for generalizing bounce buffer handling further
> to allow multiple bounce buffers, with a total allocation limit
> configured per AddressSpace.
>
> Signed-off-by: Mattias Nissler <mnissler@rivosinc.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2023-09-19 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:08 [PATCH v4 0/5] Support message-based DMA in vfio-user server Mattias Nissler
2023-09-19 16:08 ` [PATCH v4 1/5] softmmu: Per-AddressSpace bounce buffering Mattias Nissler
2023-09-19 17:12 ` Peter Xu [this message]
2023-09-19 16:08 ` [PATCH v4 2/5] softmmu: Support concurrent bounce buffers Mattias Nissler
2023-09-19 17:14 ` Peter Xu
2023-09-19 18:14 ` Mattias Nissler
2023-09-19 16:08 ` [PATCH v4 3/5] Update subprojects/libvfio-user Mattias Nissler
2023-09-19 16:08 ` [PATCH v4 4/5] vfio-user: Message-based DMA support Mattias Nissler
2023-09-19 16:08 ` [PATCH v4 5/5] vfio-user: Fix config space access byte order Mattias Nissler
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=ZQnWech0biGUuTHh@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.levon@nutanix.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mnissler@rivosinc.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.