mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sheng Zhao <sheng.zhao@bytedance.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	xieyongji@bytedance.com
Subject: Re: [External] Re: [PATCH] vduse: Use fixed 4KB bounce pages for arm64 64KB page size
Date: Mon, 15 Sep 2025 19:07:47 +0800	[thread overview]
Message-ID: <328b3f8f-cca7-4d8f-9335-24341b40b2d5@bytedance.com> (raw)
In-Reply-To: <CACGkMEvWNOjFU0pgiS=LF2B+yEC-y_RU3w_P5_dr10RPH+5xrg@mail.gmail.com>



在 2025/9/15 16:21, Jason Wang 写道:
> On Mon, Sep 15, 2025 at 3:34 PM <sheng.zhao@bytedance.com> wrote:
>>
>> From: Sheng Zhao <sheng.zhao@bytedance.com>
>>
>> The allocation granularity of bounce pages is PAGE_SIZE. This may cause
>> even small IO requests to occupy an entire bounce page exclusively.
> 
> This sounds more like an issue of the IOVA allocating that use the
> wrong granular?
> 

Sorry, the previous email has a slight formatting issue.

The granularity of the IOVA allocator is customized during the 
initialization of the vduse domain, and this value is also modified in
this commit.

Thanks

>> The
>> kind of memory waste will be more significant on arm64 with 64KB pages.
>>
>> So, optimize it by using fixed 4KB bounce pages.
>>
>> Signed-off-by: Sheng Zhao <sheng.zhao@bytedance.com>
> 
> Thanks
> 


  reply	other threads:[~2025-09-15 11:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  7:34 sheng.zhao
2025-09-15  8:21 ` Jason Wang
2025-09-15 11:07   ` Sheng Zhao [this message]
2025-09-16  7:34     ` [External] " Jason Wang
2025-09-16 13:54       ` Sheng Zhao
2025-09-17  8:16 ` Jason Wang
2025-09-23 12:37   ` Sheng Zhao
2025-09-24  0:57     ` Jason Wang
2025-09-24  4:05       ` Sheng Zhao
2025-09-24  4:15         ` Jason Wang
2025-09-24  6:38           ` Sheng Zhao
2025-09-25  0:20             ` Jason Wang
2025-09-25  3:13               ` Sheng Zhao

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=328b3f8f-cca7-4d8f-9335-24341b40b2d5@bytedance.com \
    --to=sheng.zhao@bytedance.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xieyongji@bytedance.com \
    --cc=xuanzhuo@linux.alibaba.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®