mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Tanmay Shah <tanmay.shah@amd.com>, <andersson@kernel.org>,
	<mathieu.poirier@linaro.org>, <corbet@lwn.net>,
	<skhan@linuxfoundation.org>
Cc: <linux-remoteproc@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 0/5] Enhance RPMsg buffer management
Date: Tue, 1 Sep 2026 15:03:27 +0200	[thread overview]
Message-ID: <4f8cc4b4-8c44-4d2d-befd-63911afe27a5@foss.st.com> (raw)
In-Reply-To: <20260828145853.2843486-1-tanmay.shah@amd.com>



On 8/28/26 16:58, Tanmay Shah wrote:
> Current design uses fixed (512 bytes) rpmsg buffer size in both rx and
> tx directions. This design is not suitable if the payload is larger than
> 512 bytes or the payload is very small and doesn't need that much
> memory. Instead introduce new virtio feature to retrieve rpmsg tx buf
> size and rx buf size from the virtio config space in the resource table.

This version seems good to me, with or without my suggestion in patch 4/5

Acked-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>

Thanks!

Arnaud

> 
> Changes in v8:
>    - fix commit message of 3/5, "%s/enable/Enabled"
>    - introduce new function to get buffer size for the vdev device
>    - fix description of VIRTIO_RPMSG_F_BUFSZ define
>    - "%s/or differnt RX and TX sizes)/or different RX and TX queue sizes)/"
> 
> Changes in v7:
>    - Fix 5/5 commit text, and move change log out of commit text
> 
> Changes in v6:
>    - remove buffer alignment from config space
>    - rpmsg.rst: modify alignment related documentation
> 
> Changes in v5:
>    - fix documentation about alignment of the buffer size
>    - change version field from u16 to u8
>    - remove buffer alignment check
>    - Separate buffer alignment vs MTU of a single buffer
>    - Use buffer alignment only to get next buffer address at alignment
>      boundary
> 
> Changes in v4:
>    - Introduce new patch to modify rpmsg.rst documentation
>    - check version is always 1.
>    - check size field is same as size of struct virtio_rpmsg_config
>    - introduce alignment field
>    - check alignment field is power of 2
>    - check tx and rx buf size is aligned with alignment passed in the
>      structure
>    - check msg size is < MTU size
> 
> Changes in v3:
>    - new patch [1/4] that renames variables with clear names.
>    - %s/rbufs/rx_bufs/
>    - %s/sbufs/tx_bufs/
>    - %s/last_sbuf/last_tx_buf/
>    - add num_rx_buf and num_tx_buf in the documentation
>    - change version field from u16 to u8
>    - introduce size field in the rpmsg_virtio_config structure
>    - check version field is set to any non-zero value.
>    - check size field is not 0.
>    - Remove field for private config, as not needed for now.
>    - add documentation of rpmsg_virtio_config structure
>    - Check for error when retrieving MTU size in the sample driver
>    - %s/mtu/MTU/
> 
> Changes in v2:
>    - Change author
>    - fix commit message with better explanation
>    - %s/sbuf/tx_buf
>    - %s/rbuf/rx_buf
>    - %s/num_rbuf/num_rx_buf/
>    - %s/num_sbuf/num_tx_buf/
>    - %s/sbuf_size/tx_buf_size/
>    - %s/rbuf_size/rx_buf_size/
>    - fix typo
>    - do not use ALIGN on buf size, rely on allocator
>    - make err msg more explicit, %s/vdev config:/bad vdev config/
>    - fix license and add AMD copyrights in the header virtio_rpmsg.h
>    - Assign bit 1 to VIRTIO_RPMSG_F_BUFSZ feature
>    - use __virtio32 over __u32
>    - add version field to virtio rpmsg config structure
>    - Introduce new patch to print rpmsg mtu size in the sample rpmsg driver
>    - move linux/virtio_rpmsg.h to linux/rpmsg/virtio_rpmsg.h
> 
> 
> Tanmay Shah (5):
>    rpmsg: virtio_rpmsg_bus: rename rbufs and sbufs
>    rpmsg: virtio_rpmsg_bus: allow different size of tx and rx bufs
>    rpmsg: virtio_rpmsg_bus: get buffer size from config space
>    docs: rpmsg: add virtio config space details
>    samples: rpmsg: add MTU size info
> 
>   Documentation/staging/rpmsg.rst     |  17 +++
>   drivers/rpmsg/virtio_rpmsg_bus.c    | 156 +++++++++++++++++++---------
>   include/linux/rpmsg/virtio_rpmsg.h  |  41 ++++++++
>   samples/rpmsg/rpmsg_client_sample.c |  20 +++-
>   4 files changed, 186 insertions(+), 48 deletions(-)
>   create mode 100644 include/linux/rpmsg/virtio_rpmsg.h
> 
> 
> base-commit: d4d61a4b0a52e8f3cdb3e1578602850a3452ec3e


  parent reply	other threads:[~2026-09-01 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 14:58 Tanmay Shah
2026-08-28 14:58 ` [PATCH v8 1/5] rpmsg: virtio_rpmsg_bus: rename rbufs and sbufs Tanmay Shah
2026-08-28 14:58 ` [PATCH v8 2/5] rpmsg: virtio_rpmsg_bus: allow different size of tx and rx bufs Tanmay Shah
2026-08-28 14:58 ` [PATCH v8 3/5] rpmsg: virtio_rpmsg_bus: get buffer size from config space Tanmay Shah
2026-08-28 14:58 ` [PATCH v8 4/5] docs: rpmsg: add virtio config space details Tanmay Shah
2026-09-01 12:56   ` Arnaud POULIQUEN
2026-08-28 14:58 ` [PATCH v8 5/5] samples: rpmsg: add MTU size info Tanmay Shah
2026-09-01 13:03 ` Arnaud POULIQUEN [this message]
2026-09-03 15:28   ` [PATCH v8 0/5] Enhance RPMsg buffer management Shah, Tanmay
2026-09-04 20:25     ` Mathieu Poirier

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=4f8cc4b4-8c44-4d2d-befd-63911afe27a5@foss.st.com \
    --to=arnaud.pouliquen@foss.st.com \
    --cc=andersson@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tanmay.shah@amd.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

all inboxes | Powered by JetHome®