From: Raju Rangoju <Raju.Rangoju@amd.com>
To: Dave Jiang <dave.jiang@intel.com>,
jdmason@kudzu.us, allenbh@gmail.com, ntb@lists.linux.dev
Cc: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Subject: Re: ntb_perf max chunk order
Date: Wed, 24 Jan 2024 00:19:27 +0530 [thread overview]
Message-ID: <caa29dc8-2463-b727-3283-2889cbe210a1@amd.com> (raw)
In-Reply-To: <eb872f9f-03f8-4a25-a3b2-e338833a9966@intel.com>
On 1/16/2024 9:43 PM, Dave Jiang wrote:
>
>
> On 1/16/24 00:10, Raju Rangoju wrote:
>> Hi,
>>
>> Could you please explain why net_perf does not support larger chunk sizes? Currently only MAX_CHUNK_ORDER 20 is supported (1M and below)
>
> It has to do with the limitation of Linux dma_alloc_coherent() call. Allocating physically (or IOVA) contiguous memory that's extremely large is difficult. In the past, you can do it with limited success up to 8MB with help from IOMMU as I recall. For experimental and testing purposes, you can try larger sizes.
Sure Dave, I'll explore that. Thank you.
>>
>> Thanks,
>> Raju
>>
prev parent reply other threads:[~2024-01-23 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 7:10 ntb_perf max chunk order Raju Rangoju
2024-01-16 16:13 ` Dave Jiang
2024-01-23 18:49 ` Raju Rangoju [this message]
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=caa29dc8-2463-b727-3283-2889cbe210a1@amd.com \
--to=raju.rangoju@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=ntb@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).