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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 19 Mar 2007 15:29:59 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: David Howells <dhowells@...hat.com> Cc: Kyle Moffett <mrmacman_g4@....com>, davem@...emloft.net, netdev@...r.kernel.org, herbert.xu@...hat.com, linux-kernel@...r.kernel.org, hch@...radead.org, arjan@...radead.org Subject: Re: [PATCH 0/5] [RFC] AF_RXRPC socket family implementation [try #2] > > Other RPC types use normal socket types. > > They do? Examples please. I didn't think Linux, at least, has any other RPC > socket families, though I could be wrong as I haven't made a thorough study of > them. SunRPC is implemented in user space and uses the existing TCP/IP layer and socket types, even though it is using them in an RPC manner and viewed at the RPC layer they are RPCs > I have made my client sockets use connect(), but that's just a convenience > and I need to make it possible to avoid doing that to make it useful to > the kernel. It's similar to SOCK_DGRAM sockets in this respect. So use SOCK_DGRAM, its clearly near enough. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists