From: Jan Beulich <jbeulich@suse.com>
To: Teddy Astie <teddy.astie@vates.tech>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julian Vetter" <julian.vetter@vates.tech>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6 3/3] x86/ioreq: Extend ioreq server to support multiple ioreq pages
Date: Mon, 20 Apr 2026 15:38:26 +0200 [thread overview]
Message-ID: <692cc080-ac6b-442d-b694-8e50e482856a@suse.com> (raw)
In-Reply-To: <cd9b42bf-5399-471e-9b86-dcf13eaad9e6@vates.tech>
On 20.04.2026 14:49, Teddy Astie wrote:
> Is there anything that would prevent the use of alloc_domheap_pages() to
> allocate a configuous set of pages at once; and vmap_contig() to map it
> in one go.
> That also prevents the ioreq pages from being scattered around.
>
> We would lose a few pages by aligning the size into a order, but that
> probably better than the alternatives.
>
> That way, we would only have to keep the base gfn (or first page_info)
> and size of the allocation, and don't have to use a array of mfn nor
> have to reverse the vmap to track it.
Well, higher-order allocations can easily fail when there's ample memory
available. Hence why a goal ought to be to avoid such allocations at
runtime. That's why we (now) have vmalloc() and xvmalloc().
Jan
next prev parent reply other threads:[~2026-04-20 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 9:38 [PATCH v6 0/3] Support multiple ioreq pages Julian Vetter
2026-04-20 9:38 ` [PATCH v6 1/3] ioreq: switch ioreq page allocation to vmap Julian Vetter
2026-08-18 13:06 ` Jan Beulich
2026-08-25 14:19 ` Julian Vetter
2026-08-25 14:43 ` Jan Beulich
2026-08-26 8:33 ` George Dunlap
2026-04-20 9:38 ` [PATCH v6 2/3] ioreq: Indent ioreq_server_alloc_mfn() body one level deeper Julian Vetter
2026-08-18 13:11 ` Jan Beulich
2026-04-20 9:38 ` [PATCH v6 3/3] x86/ioreq: Extend ioreq server to support multiple ioreq pages Julian Vetter
2026-04-20 12:49 ` Teddy Astie
2026-04-20 13:38 ` Jan Beulich [this message]
2026-08-18 13:57 ` Jan Beulich
2026-04-20 10:05 ` [PATCH v6 0/3] Support " Jan Beulich
2026-08-18 14:08 ` Jan Beulich
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=692cc080-ac6b-442d-b694-8e50e482856a@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=julian.vetter@vates.tech \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.org \
/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.