From: Jon Maloy <jmaloy@redhat.com>
To: passt-dev@passt.top
Subject: Re: [RFC 01/12] ip: Introduce multi-address data structures for IPv4 and IPv6
Date: Mon, 15 Dec 2025 20:58:32 -0500 [thread overview]
Message-ID: <4dd738bc-b5fa-4fee-81a1-e4cd74f15f69@redhat.com> (raw)
In-Reply-To: <aff1dbc4-26ca-4942-a609-4ce3d9db9f88@redhat.com>
On 2025-12-15 17:05, Jon Maloy wrote:
>
>
> On 2025-12-15 04:40, David Gibson wrote:
[...]
>>> +struct ip4_addr_entry {
>>> + struct in_addr addr;
>>> + int prefix_len;
>>> + int permanent;
>>
>> Might as well make these uint8_t and bool, respectively. There will
>> be some padding, but the overall structure will still be smaller.
>>
>> Or, it might be worth considering replacing 'permanent' with a flags
>> mask, in case we have future uses for it.
>
> Agree with that. I'll make that change, and if we ver need more we can
> replace the boolean with a bitmask.
> /jon
>
Provided we agree on keeping guest side subscriptions, we could mark
the address entries "guest_side" and "host_side", hence giving only
the owning side the right to remove/alter the entry.
/j
>
>>
>
next prev parent reply other threads:[~2025-12-16 1:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 1:54 [RFC 00/12] Support for multiple address and late binding Jon Maloy
2025-12-15 1:54 ` [RFC 01/12] ip: Introduce multi-address data structures for IPv4 and IPv6 Jon Maloy
2025-12-15 9:40 ` David Gibson
2025-12-15 22:05 ` Jon Maloy
2025-12-16 1:58 ` Jon Maloy [this message]
2025-12-16 3:14 ` David Gibson
2025-12-15 9:46 ` David Gibson
2025-12-15 1:54 ` [RFC 02/12] ip: Add ip4_default_prefix_len() helper function for class-based prefix Jon Maloy
2025-12-15 9:41 ` David Gibson
2025-12-15 1:54 ` [RFC 03/12] conf: Allow multiple -a/--address options per address family Jon Maloy
2025-12-15 9:53 ` David Gibson
2025-12-15 1:54 ` [RFC 04/12] conf: Apply -n/--netmask to most recently added address Jon Maloy
2025-12-15 9:54 ` David Gibson
2025-12-15 22:43 ` Jon Maloy
2025-12-15 1:54 ` [RFC 05/12] fwd: Check all configured addresses in guest accessibility functions Jon Maloy
2025-12-15 10:06 ` David Gibson
2025-12-15 1:54 ` [RFC 06/12] arp: Check all configured addresses in ARP filtering Jon Maloy
2025-12-15 10:07 ` David Gibson
2025-12-15 1:54 ` [RFC 07/12] netlink: Subscribe to link/address changes in namespace Jon Maloy
2025-12-15 10:32 ` David Gibson
2025-12-15 23:25 ` Jon Maloy
2025-12-16 3:21 ` David Gibson
2025-12-15 1:54 ` [RFC 08/12] netlink: Subscribe to route " Jon Maloy
2025-12-15 10:38 ` David Gibson
2025-12-15 1:54 ` [RFC 09/12] netlink: Add host-side monitoring for late template interface binding Jon Maloy
2025-12-15 1:54 ` [RFC 10/12] netlink: Add host-side route monitoring and propagation Jon Maloy
2025-12-15 1:54 ` [RFC 11/12] netlink: Prevent host route events from overwriting guest-configured gateway Jon Maloy
2025-12-15 1:54 ` [RFC 12/12] netlink: Rename tap interface when late binding discovers template name Jon Maloy
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=4dd738bc-b5fa-4fee-81a1-e4cd74f15f69@redhat.com \
--to=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
/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).