netdev - Re: [PATCH net-next v4 01/12] inet: 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] [day] [month] [year] [list]

Message-ID: <CAGXJAmxaCcbJy5cygga13WegYTMp-LeD3KCdBYE24Eow=qoZDg@mail.gmail.com>
Date: Fri, 20 Dec 2024 15:51:36 -0800
From: John Ousterhout <ouster@...stanford.edu>
To: Arnd Bergmann <arnd@...db.de>
Cc: Jakub Kicinski <kuba@...nel.org>, Netdev <netdev@...r.kernel.org>, 
	Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>, Simon Horman <horms@...nel.org>
Subject: Re: [PATCH net-next v4 01/12] inet: homa: define user-visible API for Homa

On Fri, Dec 20, 2024 at 3:42 PM John Ousterhout <ouster@...stanford.edu> wrote:
>
> I hadn't considered this, but the buffering mechanism prevents the
> same socket from being shared across processes.

It just occurred to me that a Homa socket should be sharable by
multiple processes as long as the buffer region is also shared at the
same virtual address in each process.

-John-