public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 4/8] fwd: Move port exclusion handling from procfs_scan_listen() to callers
Date: Mon, 3 Nov 2025 12:43:53 +1100	[thread overview]
Message-ID: <aQgI2dPsrl7IAL_R@zatzit> (raw)
In-Reply-To: <20251031092120.07ad0392@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]

On Fri, Oct 31, 2025 at 09:21:20AM +0100, Stefano Brivio wrote:
> On Fri, 31 Oct 2025 13:47:10 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Thu, Oct 30, 2025 at 09:24:04PM +0100, Stefano Brivio wrote:
> > > On Sat, 11 Oct 2025 15:48:23 +1100
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
[snip]
> > > >  void bitmap_or(uint8_t *dst, size_t size, const uint8_t *a, const uint8_t *b)
> > > >  {
> > > >  	unsigned long *dw = (unsigned long *)dst;
> > > > @@ -365,6 +367,27 @@ void bitmap_or(uint8_t *dst, size_t size, const uint8_t *a, const uint8_t *b)
> > > >  		dst[i] = a[i] | b[i];
> > > >  }
> > > >  
> > > > +/**
> > > > + * bitmap_andc() - Logical conjunction with complement (AND NOT) of bitmap  
> > > 
> > > Nit: this function name mixes classic logic terminology (conjunction,
> > > complement) and operator names (and, not), which makes it hard to guess,
> > > I think.  
> > 
> > That's my POWER background showing:
> >     https://www.ibm.com/docs/en/aix/7.3.0?topic=set-andc-complement-instruction
> 
> I obviously don't have a POWER background but I do remember a couple of
> instructions simply because I found their names hilariously dissonant
> (other than finding them in whatever disassembly I was looking at). My
> favourite mouthful is RLWIMI:

Yes, rlwimi is fun.  Along with rlwimn, and once you go 64-bit rldimi,
rldicr and rldicl.  They're utterly inscrutable when you first
encounter them, but are super useful and natural once you get used to
them.  Well, rlwimi and rlwimn at least.  The 64-bit bit versions are
upsettingly less general, simply because there aren't enough bits in
an instruction to encode true equivalents of the 32-bit versions.

>   https://www.ibm.com/docs/en/openxl-c-and-cpp-aix/17.1.3?topic=rf-rldimi-builtin-ppc-rldimi-rlwimi-builtin-ppc-rlwimi
> 
> but ANDC is also remarkable (cf. ANDN in the successful CISC set,
> which obviously sounds like the only right choice to me).

And, of course, there's "eieio".

-- 
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 --]

  reply	other threads:[~2025-11-03  1:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  4:48 [PATCH 0/8] RFC: Cleanups to auto port scanning David Gibson
2025-10-11  4:48 ` [PATCH 1/8] icmp: Remove vestiges of ICMP timer David Gibson
2025-10-11  4:48 ` [PATCH 2/8] tcp, udp, fwd: Run all port scanning from a single timer David Gibson
2025-10-11  4:48 ` [PATCH 3/8] fwd: Consolidate scans (not rebinds) in fwd.c David Gibson
2025-10-11  4:48 ` [PATCH 4/8] fwd: Move port exclusion handling from procfs_scan_listen() to callers David Gibson
2025-10-30 20:24   ` Stefano Brivio
2025-10-31  2:47     ` David Gibson
2025-10-31  8:21       ` Stefano Brivio
2025-11-03  1:43         ` David Gibson [this message]
2025-10-11  4:48 ` [PATCH 5/8] fwd: Share port scanning logic between init and timer cases David Gibson
2025-10-11  4:48 ` [PATCH 6/8] fwd: Check forwarding mode in fwd_scan_ports_*() rather than caller David Gibson
2025-10-11  4:48 ` [PATCH 7/8] fwd: Update all port maps before applying exclusions David Gibson
2025-10-30 20:24   ` Stefano Brivio
2025-10-31  2:51     ` David Gibson
2025-10-11  4:48 ` [PATCH 8/8] tcp, udp: Don't exclude ports in {tcp,udp}_port_rebind() David Gibson

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=aQgI2dPsrl7IAL_R@zatzit \
    --to=david@gibson.dropbear.id.au \
    --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).