From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v2 1/8] icmp, udp: Pad time_t timestamp to 64-bit to ease state migration
Date: Wed, 29 Jan 2025 12:34:48 +1100 [thread overview]
Message-ID: <Z5mFuJkg8a3xUi0A@zatzit> (raw)
In-Reply-To: <20250128233940.1235855-2-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Wed, Jan 29, 2025 at 12:39:33AM +0100, Stefano Brivio wrote:
> That's the only field in flows with different storage sizes depending
> on the architecture: it's usually 4-byte wide on 32-bit architectures,
> except for arc and x32 where it's 8 bytes, and 8-byte wide on 64-bit
> machines.
>
> By keeping flow entries the same size across architectures, we avoid
> having to expand or shrink table entries upon migration.
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Ugly, but necessary for this v1 approach.
> ---
> icmp_flow.h | 6 +++++-
> udp_flow.h | 6 +++++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/icmp_flow.h b/icmp_flow.h
> index fb93801..da7e255 100644
> --- a/icmp_flow.h
> +++ b/icmp_flow.h
> @@ -13,6 +13,7 @@
> * @seq: Last sequence number sent to tap, host order, -1: not sent yet
> * @sock: "ping" socket
> * @ts: Last associated activity from tap, seconds
> + * @ts_storage: Pad @ts to 64-bit storage to keep state migration sane
> */
> struct icmp_ping_flow {
> /* Must be first element */
> @@ -20,7 +21,10 @@ struct icmp_ping_flow {
>
> int seq;
> int sock;
> - time_t ts;
> + union {
> + time_t ts;
> + uint64_t ts_storage;
> + };
> };
>
> bool icmp_ping_timer(const struct ctx *c, const struct icmp_ping_flow *pingf,
> diff --git a/udp_flow.h b/udp_flow.h
> index 9a1b059..9cb79a0 100644
> --- a/udp_flow.h
> +++ b/udp_flow.h
> @@ -12,6 +12,7 @@
> * @f: Generic flow information
> * @closed: Flow is already closed
> * @ts: Activity timestamp
> + * @ts_storage: Pad @ts to 64-bit storage to keep state migration sane
> * @s: Socket fd (or -1) for each side of the flow
> */
> struct udp_flow {
> @@ -19,7 +20,10 @@ struct udp_flow {
> struct flow_common f;
>
> bool closed :1;
> - time_t ts;
> + union {
> + time_t ts;
> + uint64_t ts_storage;
> + };
> int s[SIDES];
> };
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-29 4:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 23:39 [PATCH v2 0/8] Draft, incomplete series introducing state migration Stefano Brivio
2025-01-28 23:39 ` [PATCH v2 1/8] icmp, udp: Pad time_t timestamp to 64-bit to ease " Stefano Brivio
2025-01-29 1:34 ` David Gibson [this message]
2025-01-28 23:39 ` [PATCH v2 2/8] flow, flow_table: Pad flow table entries to 128 bytes, hash entries to 32 bits Stefano Brivio
2025-01-29 1:35 ` David Gibson
2025-01-28 23:39 ` [PATCH v2 3/8] flow_table: Use size in extern declaration for flowtab Stefano Brivio
2025-01-28 23:39 ` [PATCH v2 4/8] util: Add read_remainder() and read_all_buf() Stefano Brivio
2025-01-29 1:37 ` David Gibson
2025-01-28 23:39 ` [PATCH v2 5/8] Introduce facilities for guest migration on top of vhost-user infrastructure Stefano Brivio
2025-01-29 5:41 ` David Gibson
2025-01-29 8:46 ` Stefano Brivio
2025-01-30 1:28 ` David Gibson
2025-01-28 23:39 ` [PATCH v2 6/8] Introduce passt-repair Stefano Brivio
2025-01-28 23:39 ` [PATCH v2 7/8] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-01-29 6:09 ` David Gibson
2025-01-29 8:46 ` Stefano Brivio
2025-01-30 1:33 ` David Gibson
2025-01-28 23:39 ` [PATCH v2 8/8] flow, tcp: Basic pre-migration source handler to dump sequence numbers Stefano Brivio
2025-01-29 6:15 ` David Gibson
2025-01-29 8:46 ` Stefano Brivio
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=Z5mFuJkg8a3xUi0A@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).