netdev - Re: [PATCH net-next 01/12] net: homa: define user-visible API for Homa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGXJAmzuKXyfiercDz-Hxf6J1xoNV=5Bv9cz1Y4HSrBY5vPviQ@mail.gmail.com>
Date: Fri, 1 Nov 2024 10:47:20 -0700
From: John Ousterhout <ouster@...stanford.edu>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 01/12] net: homa: define user-visible API for Homa

On Wed, Oct 30, 2024 at 5:41 AM Andrew Lunn <andrew@...n.ch> wrote:
>
> > > Did you build for 32 bit systems?
> >
> > Sadly no: my development system doesn't currently have any
> > cross-compiling versions of gcc :-(
>
> I'm not sure in this case it is actually a cross compile. Your default
> amd64 tool chain should also be able to compile for i386.
>
> export ARCH=i386
> unset CROSS_COMPILE
> make defconfig
> make

Thanks for this additional information. I have now compiled Homa
(along with the rest of the kernel) for ARCH=i386; in the process I
learned about uintptr_t and do_div.

Question: is the distinction between the types u64 and __u64
significant? If so, is there someplace where it is explained when I
should use each? So far I have been using __u64 (almost) everywhere.

-John-