From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Getting + maintaining a consistent MDB view in userspace?
Date: Tue, 8 Aug 2023 02:29:09 +0200 [thread overview]
Message-ID: <ZNGMVUNsZWWUd7so@sellars> (raw)
Hi,
Is there a recommended way to get and monitor the MDB state from
userspace, without potential synchronization races?
I can use "bridge monitor mdb" to get changes or "bridge mdb show"
to get the current state (as well as use the underlying netlink
calls from my own application without the "bridge" command).
But if I were first calling "bridge mdb show" and then "bridge
monitor mdb" then there is a brief moment where I might miss some
changes. Or if I were doing it the other way around then a change
might wrongly override a valid entry? Or the full dump might not
be as up to date as the change event I got before?
Ideally I'd be looking for a variant of "bridge monitor mdb" which
first dumps the whole, consistent mdb state and after that
provides updates in the correct order.
Regards, Linus
next reply other threads:[~2023-08-08 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 0:29 Linus Lüssing [this message]
2023-08-08 1:20 ` [Bridge] Getting + maintaining a consistent MDB view in userspace? Stephen Hemminger
2023-08-09 22:56 ` Linus Lüssing
2023-08-10 2:07 ` Linus Lüssing
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=ZNGMVUNsZWWUd7so@sellars \
--to=linus.luessing@c0d3.blue \
--cc=bridge@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox