All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	herbert.xu@redhat.com, linux-kernel@vger.kernel.org,
	hch@infradead.org, arjan@infradead.org
Subject: Re: [PATCH 0/5] [RFC] AF_RXRPC socket family implementation [try #2]
Date: Mon, 19 Mar 2007 15:41:38 +0000	[thread overview]
Message-ID: <25752.1174318898@redhat.com> (raw)
In-Reply-To: <20070319152959.46a81e57@lxorguk.ukuu.org.uk>

Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

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

SunRPC is not then a suitable analogy.  There is no socket interface that
provides SunRPC as far as I know, so your example is invalid.  Yes, SunRPC is
built on top of something else, SOCK_DGRAM, SOCK_STREAM or whatever, but that's
like saying TCP is a datagram service rather than a stream service because it's
built on a datagram service (IP).  What a protocol uses out the back is pretty
much irrelevant - what is relevant is what the protocol in question actually
appears to provide to anyone using it.

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

No, it's not.  SOCK_DGRAM is an unreliable, unidirectional datagram passing
service.

David

  reply	other threads:[~2007-03-19 15:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 12:50 [PATCH 0/5] [RFC] AF_RXRPC socket family implementation [try #2] David Howells
2007-03-16 12:50 ` [PATCH 1/5] AF_RXRPC: Add blkcipher accessors for using kernel data directly " David Howells
2007-03-16 13:32   ` Christoph Hellwig
2007-03-16 13:57     ` David Howells
2007-03-16 15:12       ` Alan Cox
2007-03-16 14:19         ` David Howells
2007-03-16 12:50 ` [PATCH 2/5] AF_RXRPC: Move generic skbuff stuff from XFRM code to generic code " David Howells
2007-03-16 13:36   ` Christoph Hellwig
2007-03-16 12:50 ` [PATCH 3/5] AF_RXRPC: Make it possible to merely try to cancel timers and delayed work " David Howells
2007-03-16 15:07   ` Alan Cox
2007-03-16 14:22     ` David Howells
2007-03-16 12:50 ` [PATCH 4/5] AF_RXRPC: Key facility changes for AF_RXRPC " David Howells
2007-03-16 13:38   ` Christoph Hellwig
2007-03-16 14:15     ` David Howells
2007-03-16 13:40 ` [PATCH 0/5] [RFC] AF_RXRPC socket family implementation " Christoph Hellwig
2007-03-16 15:13 ` Alan Cox
2007-03-16 14:23   ` David Howells
2007-03-16 15:34     ` Alan Cox
2007-03-16 15:14       ` David Howells
2007-03-16 17:11         ` Alan Cox
2007-03-18  6:32           ` Kyle Moffett
2007-03-18 14:23             ` Alan Cox
2007-03-19 11:56               ` David Howells
2007-03-19 13:04                 ` Alan Cox
2007-03-19 12:59                   ` David Howells
2007-03-19 15:29                     ` Alan Cox
2007-03-19 15:41                       ` David Howells [this message]
2007-03-19 19:03                         ` Alan Cox
2007-03-20 11:16                           ` David Howells
2007-03-19 19:19                         ` David Miller
2007-03-20 13:16                           ` David Howells

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=25752.1174318898@redhat.com \
    --to=dhowells@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=herbert.xu@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=netdev@vger.kernel.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.