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: <98864170-ac97-43c9-b8b2-39fd02ac198a@lunn.ch>
Date: Fri, 20 Dec 2024 22:18:10 +0100
From: Andrew Lunn <andrew@...n.ch>
To: John Ousterhout <ouster@...stanford.edu>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
	pabeni@...hat.com, edumazet@...gle.com, 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 09:59:53AM -0800, John Ousterhout wrote:
> On Thu, Dec 19, 2024 at 5:41 PM Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > > Any suggestions on how to make the header file work with C++ files
> > > without the #ifdef __cplusplus?
> >
> > With the little C++ understanding I have, I _think_ the include site
> > can wrap:
> >
> > extern "C" {
> > #include "<linux/homa.h>"
> > }
> 
> I have done this now. I was hesitant to do that because it seemed like
> it was creating unnecessary extra work for anyone who uses homa.h in a
> C++ program, but since this seems to be the convention I have
> conformed to it.

Do C++ programmes directly use this header, or is there a library in
the middle?

Often kernel APIs are too low level for an application to use
directly, and a library is used to provide a higher level API. That
would allow you to provide a different header file which is more C++
friendly.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ