DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Vipin Varghese <vipin.varghese@amd.com>, <dev@dpdk.org>,
	<stable@dpdk.org>, <honest.jiang@foxmail.com>
Subject: Re: [PATCH] doc: update size parameter details
Date: Thu, 7 Mar 2024 21:27:01 +0800	[thread overview]
Message-ID: <3dc0dccf-190c-0588-1927-ecb865400d30@huawei.com> (raw)
In-Reply-To: <20231212104508.1941-1-vipin.varghese@amd.com>

Hi Vipin,

On 2023/12/12 18:45, Vipin Varghese wrote:
> For configuration parameters `mem_size` and `buf_size` are represented
> as megabytes and bytes respectively in application. Update the
> documentation to represent the same.
> 
> Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
> ---
>  doc/guides/tools/dmaperf.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/guides/tools/dmaperf.rst b/doc/guides/tools/dmaperf.rst
> index 9e3e78a6b7..6f85fceb8a 100644
> --- a/doc/guides/tools/dmaperf.rst
> +++ b/doc/guides/tools/dmaperf.rst
> @@ -74,10 +74,10 @@ Configuration Parameters
>    Currently supported types are ``DMA_MEM_COPY`` and ``CPU_MEM_COPY``.
>  
>  ``mem_size``
> -  The size of the memory footprint.
> +  The size of the memory footprint in megabytes (MB) for source and destination.

I prefer not add "for source and destination", it makes sense without this, and maybe future test like fill don't have source buffer.

>  
>  ``buf_size``
> -  The memory size of a single operation.
> +  The memory size of a single operation in bytes (B).
>  
>  ``dma_ring_size``
>    The DMA ring buffer size. Must be a power of two, and between ``64`` and ``4096``.
> 

BTW: Could you please also modify the app/test-dma-perf/config.ini (which also missing this)

Thanks

  parent reply	other threads:[~2024-03-07 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 10:45 Vipin Varghese
2024-03-06  6:08 ` Varghese, Vipin
2024-03-07 13:27 ` fengchengwen [this message]
2024-03-07 15:50   ` Varghese, Vipin
2024-03-12  4:22 ` [PATCH v2] " Vipin Varghese
2024-03-12  6:07   ` fengchengwen
2024-03-12  6:17     ` fengchengwen
2024-03-18  2:47       ` Thomas Monjalon

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=3dc0dccf-190c-0588-1927-ecb865400d30@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=dev@dpdk.org \
    --cc=honest.jiang@foxmail.com \
    --cc=stable@dpdk.org \
    --cc=vipin.varghese@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;
as well as URLs for NNTP newsgroup(s).