qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Hailiang Zhang" <zhanghailiang@xfusion.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Fam Zheng" <fam@euphon.net>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	qemu-block@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: [PULL 09/25] migration: rename 'pos' field in QEMUFile to 'bytes_processed'
Date: Wed, 22 Jun 2022 02:25:31 +0200	[thread overview]
Message-ID: <20220622002547.64784-10-quintela@redhat.com> (raw)
In-Reply-To: <20220622002547.64784-1-quintela@redhat.com>

From: Daniel P. Berrangé <berrange@redhat.com>

The field name 'pos' gives the misleading impression that the QEMUFile
objects are seekable. This is not the case, as in general we just
have an opaque stream. The users of this method are only interested
in the total bytes processed. This switches to a new name that
reflects the intended usage.

Every QIOChannel backed impl of QEMUFile is currently ignoring the
'pos' field.

The only QEMUFile impl using 'pos' as an offset for I/O is the block
device vmstate. A later patch is introducing a QIOChannel impl for the
vmstate, and to handle this it is tracking a file offset itself
internally to the QIOChannel impl. So when we later eliminate the
QEMUFileOps callbacks later, the 'pos' field will no longer be used
from any I/O read/write methods.

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
 migration/qemu-file.c | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/migration/qemu-file.c b/migration/qemu-file.c
index 03f0b13a55..b21da4c5bf 100644
--- a/migration/qemu-file.c
+++ b/migration/qemu-file.c
@@ -50,8 +50,9 @@ struct QEMUFile {
      */
     int64_t rate_limit_used;
 
-    int64_t pos; /* start of buffer when writing, end of buffer
-                    when reading */
+    /* The sum of bytes transferred on the wire */
+    int64_t total_transferred;
+
     int buf_index;
     int buf_size; /* 0 when writing */
     uint8_t buf[IO_BUF_SIZE];
@@ -241,14 +242,14 @@ void qemu_fflush(QEMUFile *f)
     }
     if (f->iovcnt > 0) {
         expect = iov_size(f->iov, f->iovcnt);
-        ret = f->ops->writev_buffer(f->opaque, f->iov, f->iovcnt, f->pos,
+        ret = f->ops->writev_buffer(f->opaque, f->iov, f->iovcnt, f->total_transferred,
                                     &local_error);
 
         qemu_iovec_release_ram(f);
     }
 
     if (ret >= 0) {
-        f->pos += ret;
+        f->total_transferred += ret;
     }
     /* We expect the QEMUFile write impl to send the full
      * data set we requested, so sanity check that.
@@ -357,11 +358,11 @@ static ssize_t qemu_fill_buffer(QEMUFile *f)
         return 0;
     }
 
-    len = f->ops->get_buffer(f->opaque, f->buf + pending, f->pos,
+    len = f->ops->get_buffer(f->opaque, f->buf + pending, f->total_transferred,
                              IO_BUF_SIZE - pending, &local_error);
     if (len > 0) {
         f->buf_size += len;
-        f->pos += len;
+        f->total_transferred += len;
     } else if (len == 0) {
         qemu_file_set_error_obj(f, -EIO, local_error);
     } else if (len != -EAGAIN) {
@@ -375,7 +376,7 @@ static ssize_t qemu_fill_buffer(QEMUFile *f)
 
 void qemu_update_position(QEMUFile *f, size_t size)
 {
-    f->pos += size;
+    f->total_transferred += size;
 }
 
 /** Closes the file
@@ -658,7 +659,7 @@ int qemu_get_byte(QEMUFile *f)
 
 int64_t qemu_ftell_fast(QEMUFile *f)
 {
-    int64_t ret = f->pos;
+    int64_t ret = f->total_transferred;
     int i;
 
     for (i = 0; i < f->iovcnt; i++) {
@@ -671,7 +672,7 @@ int64_t qemu_ftell_fast(QEMUFile *f)
 int64_t qemu_ftell(QEMUFile *f)
 {
     qemu_fflush(f);
-    return f->pos;
+    return f->total_transferred;
 }
 
 int qemu_file_rate_limit(QEMUFile *f)
-- 
2.35.3



  parent reply	other threads:[~2022-06-22  0:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  0:25 [PULL 00/25] Migration 20220621 patches Juan Quintela
2022-06-22  0:25 ` [PULL 01/25] migration: Remove RDMA_UNREGISTRATION_EXAMPLE Juan Quintela
2022-06-22  0:25 ` [PULL 02/25] QIOChannelSocket: Introduce assert and reduce ifdefs to improve readability Juan Quintela
2022-06-22  0:25 ` [PULL 03/25] QIOChannelSocket: Fix zero-copy send so socket flush works Juan Quintela
2022-06-22  0:25 ` [PULL 04/25] migration: Change zero_copy_send from migration parameter to migration capability Juan Quintela
2022-06-22  0:25 ` [PULL 05/25] io: add a QIOChannelNull equivalent to /dev/null Juan Quintela
2022-06-22  0:25 ` [PULL 06/25] migration: switch to use QIOChannelNull for dummy channel Juan Quintela
2022-06-22  0:25 ` [PULL 07/25] migration: remove unreachble RDMA code in save_hook impl Juan Quintela
2022-06-22  0:25 ` [PULL 08/25] migration: rename rate limiting fields in QEMUFile Juan Quintela
2022-06-22  0:25 ` Juan Quintela [this message]
2022-06-22  0:25 ` [PULL 10/25] migration: rename qemu_ftell to qemu_file_total_transferred Juan Quintela
2022-06-22  0:25 ` [PULL 11/25] migration: rename qemu_update_position to qemu_file_credit_transfer Juan Quintela
2022-06-22  0:25 ` [PULL 12/25] migration: rename qemu_file_update_transfer to qemu_file_acct_rate_limit Juan Quintela
2022-06-22  0:25 ` [PULL 13/25] migration: introduce a QIOChannel impl for BlockDriverState VMState Juan Quintela
2022-06-22  0:25 ` [PULL 14/25] migration: convert savevm to use QIOChannelBlock for VMState Juan Quintela
2022-06-22  0:25 ` [PULL 15/25] migration: stop passing 'opaque' parameter to QEMUFile hooks Juan Quintela
2022-06-22  0:25 ` [PULL 16/25] migration: hardcode assumption that QEMUFile is backed with QIOChannel Juan Quintela
2022-06-22  0:25 ` [PULL 17/25] migration: introduce new constructors for QEMUFile Juan Quintela
2022-06-22  0:25 ` [PULL 18/25] migration: remove unused QEMUFileGetFD typedef / qemu_get_fd method Juan Quintela
2022-06-22  0:25 ` [PULL 19/25] migration: remove the QEMUFileOps 'shut_down' callback Juan Quintela
2022-06-22  0:25 ` [PULL 20/25] migration: remove the QEMUFileOps 'set_blocking' callback Juan Quintela
2022-06-22  0:25 ` [PULL 21/25] migration: remove the QEMUFileOps 'close' callback Juan Quintela
2022-06-22  0:25 ` [PULL 22/25] migration: remove the QEMUFileOps 'get_buffer' callback Juan Quintela
2022-06-22  0:25 ` [PULL 23/25] migration: remove the QEMUFileOps 'writev_buffer' callback Juan Quintela
2022-06-22  0:25 ` [PULL 24/25] migration: remove the QEMUFileOps 'get_return_path' callback Juan Quintela
2022-06-22  0:25 ` [PULL 25/25] migration: remove the QEMUFileOps abstraction Juan Quintela
2022-06-22  2:14 ` [PULL 00/25] Migration 20220621 patches Richard Henderson
2022-06-22 15:19   ` Dr. David Alan Gilbert
  -- strict thread matches above, loose matches on Subject: below --
2022-06-23 16:53 [PULL 00/25] migration queue Dr. David Alan Gilbert (git)
2022-06-23 16:53 ` [PULL 09/25] migration: rename 'pos' field in QEMUFile to 'bytes_processed' Dr. David Alan Gilbert (git)

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=20220622002547.64784-10-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=fam@euphon.net \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhanghailiang@xfusion.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).