All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Frediano Ziglio <freddy77@gmail.com>, xen-devel@lists.xenproject.org
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Frediano Ziglio" <frediano.ziglio@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Teddy Astie" <teddy.astie@vates.tech>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Juergen Gross" <jgross@suse.com>
Subject: Re: [PATCH v6 03/16] libs/guest: Reduce number of I/O vectors in write_batch
Date: Tue, 30 Jun 2026 17:46:55 +0100	[thread overview]
Message-ID: <73d8b955-8462-47ce-8913-d11303bf63c3@citrix.com> (raw)
In-Reply-To: <20260619130501.272832-4-frediano.ziglio@citrix.com>


This has the same exact subject as the prior patch.

Either it wants merging, as they're both in the same function, or the
subject wants to be different.  Even a "Further ..." prefix would help.

On 19/06/2026 2:04 pm, Frediano Ziglio wrote:
> Each page was sent using a different iovec item. This potentially exceed
> Linux maximum (1024).

Linux cannot have a maximum of 1024 because this has been working fine
for a decade using 1028 in the common case.

> Coalesce adjacent IO vector elements to attempt to reduce the number of
> overall IO vectors for each operation.
> Also some implementation (MiniOS) emulate writev with multiple write calls.
>
> Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com>
> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>



  reply	other threads:[~2026-06-30 16:47 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19 13:04 [PATCH v6 00/16] xenguest optimisations Frediano Ziglio
2026-06-19 13:04 ` [PATCH v6 01/16] libs/guest: Reduce number of parts in write_split_record Frediano Ziglio
2026-06-30 16:35   ` Andrew Cooper
2026-07-08  9:07   ` Anthony PERARD
2026-06-19 13:04 ` [PATCH v6 02/16] libs/guest: Reduce number of I/O vectors in write_batch Frediano Ziglio
2026-06-30 16:40   ` Andrew Cooper
2026-07-02 12:31     ` Frediano Ziglio
2026-07-01 13:52   ` [PATCH v6 1.9/16] libs/guest: Allocate rec_pfns earlier in write_batch() Andrew Cooper
2026-07-08  9:08     ` Anthony PERARD
2026-07-01 13:57   ` [PATCH v6.1 02/16] libs/guest: Reduce number of iovecs " Andrew Cooper
2026-07-08  9:09     ` Anthony PERARD
2026-06-19 13:04 ` [PATCH v6 03/16] libs/guest: Reduce number of I/O vectors in write_batch Frediano Ziglio
2026-06-30 16:46   ` Andrew Cooper [this message]
2026-07-02 12:33     ` Frediano Ziglio
2026-07-08  9:34       ` Anthony PERARD
2026-06-19 13:04 ` [PATCH v6 04/16] libs/guest: Use a single write_exact in write_headers Frediano Ziglio
2026-06-30 16:47   ` Andrew Cooper
2026-07-08  9:35     ` Anthony PERARD
2026-06-19 13:04 ` [PATCH v6 05/16] libs/guest: allocate various migration arrays just once Frediano Ziglio
2026-07-01 11:34   ` Andrew Cooper
2026-06-19 13:04 ` [PATCH v6 06/16] libs/call: cache up to 4 pages in hypercall bounce buffers Frediano Ziglio
2026-07-07 13:51   ` Anthony PERARD
2026-07-07 14:05     ` Anthony PERARD
2026-07-07 14:47     ` Frediano Ziglio
2026-07-08 13:19       ` Anthony PERARD
2026-07-09  7:13         ` Frediano Ziglio
2026-06-19 13:04 ` [PATCH v6 07/16] libs/guest: avoids using 2 indexes Frediano Ziglio
2026-07-08 13:19   ` Anthony PERARD
2026-06-19 13:04 ` [PATCH v6 08/16] libs/guest: fill directly iov structure Frediano Ziglio
2026-07-01 11:47   ` Andrew Cooper
2026-06-19 13:04 ` [PATCH v6 09/16] libs/ctrl: Allows writev_exact to change iov array Frediano Ziglio
2026-06-30 17:08   ` Andrew Cooper
2026-06-19 13:04 ` [PATCH v6 10/16] libs/guest: add xg_foreignmemory_copy_{from,to} Frediano Ziglio
2026-07-08 13:32   ` Anthony PERARD
2026-07-09 10:07     ` Frediano Ziglio
2026-06-19 13:04 ` [PATCH v6 11/16] PoC: libs/guest: use foreign copy during migration Frediano Ziglio
2026-07-08 13:55   ` Anthony PERARD
2026-07-09  9:35     ` Frediano Ziglio
2026-06-19 13:04 ` [PATCH v6 12/16] xen: implement new foreign copy hypercall Frediano Ziglio
2026-06-22 10:34   ` Jan Beulich
2026-06-23 10:55     ` Frediano Ziglio
2026-06-23 13:21       ` Jan Beulich
2026-06-23 21:18         ` Frediano Ziglio
2026-06-24  6:44           ` Jan Beulich
2026-06-26 14:14             ` Frediano Ziglio
2026-06-29  6:59               ` Jan Beulich
2026-08-03 14:51                 ` Frediano Ziglio
2026-06-22 10:44   ` Jan Beulich
2026-06-23 20:37   ` Daniel P. Smith
2026-06-19 13:04 ` [PATCH v6 13/16] privcmd: Add definition for new Linux privcmd to access new Xen hypercall Frediano Ziglio
2026-07-08 13:59   ` Anthony PERARD
2026-07-09  9:37     ` Frediano Ziglio
2026-06-19 13:04 ` [PATCH v6 14/16] libs/guest: use new hypercall if available Frediano Ziglio
2026-06-19 13:05 ` [PATCH v6 15/16] libs/guest: finalize PoC Frediano Ziglio
2026-07-08 14:12   ` Anthony PERARD
2026-07-09  9:39     ` Frediano Ziglio
2026-06-19 13:05 ` [PATCH Linux v6 16/16] xen/privcmd: Add new ABI to allow copying foreign memory Frediano Ziglio
2026-07-09 10:53   ` Juergen Gross
2026-08-03 14:05   ` Juergen Gross
2026-08-03 14:23     ` Frediano Ziglio
2026-08-03 14:52       ` Juergen Gross

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=73d8b955-8462-47ce-8913-d11303bf63c3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=freddy77@gmail.com \
    --cc=frediano.ziglio@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --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.