All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	netdev@vger.kernel.org, shemminger@vyatta.com, jj@chaosbits.net,
	daniel.baluta@gmail.com, jochen@jochen.org, hagen@jauu.net,
	torvalds@linux-foundation.org, pavel@ucw.cz
Subject: Re: [PATCH] new UDPCP Communication Protocol
Date: Tue, 11 Jan 2011 23:23:29 +0100	[thread overview]
Message-ID: <1294784609.18562.4.camel@wall-e> (raw)
In-Reply-To: <1294782386.3447.21.camel@edumazet-laptop>

Am Dienstag, den 11.01.2011, 22:46 +0100 schrieb Eric Dumazet:
> Le mardi 11 janvier 2011 à 22:41 +0100, Stefani Seibold a écrit :
> 
> > Second, the design is may in your opinion poor. I like it. What is
> > really poor is the kernel_...() socket functions, which are only simple
> > wrapper of the system calls without any performance improvement, skb
> > support and memory saving.
> > 
> 
> The only thing you want is to have a callback to your own code to
> deliver an decapsulated skb to your state machine.
> 
> Take a look at other layers on top of UDP
> 
> (L2TP comes to mind)
> 

I have looked on it. And it will not work since UDPCP is UDP. And so
IPPROTO_UDP (17) is still handled by the UDP handler.

Despite this it will also make no sense to rewrite the whole UDP socket
layer.

The only thing i have found with comes near to my requirements is the
rxrpc module, but i see no real different to my solution.



  reply	other threads:[~2011-01-11 22:22 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:48 [PATCH] new UDPCP Communication Protocol stefani
2011-01-11 16:48 ` stefani
2011-01-11 17:01 ` Eric Dumazet
2011-01-11 20:50   ` Stefani Seibold
2011-01-11 20:52     ` David Miller
2011-01-11 21:14       ` Stefani Seibold
2011-01-11 21:19         ` David Miller
2011-01-11 21:41           ` Stefani Seibold
2011-01-11 21:46             ` Eric Dumazet
2011-01-11 22:23               ` Stefani Seibold [this message]
2011-01-11 21:30         ` Eric Dumazet
2011-01-11 21:40           ` Stefani Seibold
2011-01-11 21:06     ` Eric Dumazet
  -- strict thread matches above, loose matches on Subject: below --
2011-01-03 14:34 stefani
2011-01-03 14:34 ` stefani
2011-01-02 22:39 stefani
2011-01-02 22:39 ` stefani
2011-01-02 22:49 ` Eric Dumazet
2011-01-02 22:55   ` Stefani Seibold
2011-01-02 23:04     ` Jesper Juhl
2011-01-03  9:08       ` Stefani Seibold
2011-01-03  9:27         ` Eric Dumazet
2011-01-03  9:54           ` Stefani Seibold
2011-01-03 10:39             ` Eric Dumazet
2011-01-03 14:08               ` Stefani Seibold
2011-01-02 15:31 stefani
2011-01-02 16:34 ` Eric Dumazet
2011-01-02 19:48 ` Daniel Baluta
2011-01-02 21:33   ` Stefani Seibold
2011-01-02 21:40     ` Jesper Juhl
2011-01-02 19:55 ` Jesper Juhl
2011-01-02 21:46   ` Stefani Seibold
2011-01-02 22:04     ` Jesper Juhl
2011-01-02 22:21       ` Stefani Seibold
2011-01-02 20:16 ` Rémi Denis-Courmont
2011-01-02 21:37   ` Stefani Seibold
2011-01-02 21:55 ` Eric Dumazet
2011-01-02 22:16   ` Stefani Seibold
2011-01-02 22:31     ` Eric Dumazet
2011-01-01 21:44 stefani
2011-01-01 22:23 ` Eric Dumazet
2011-01-02 11:17   ` Stefani Seibold
2011-01-02 11:33     ` Eric Dumazet
2011-01-02 11:57       ` Stefani Seibold

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=1294784609.18562.4.camel@wall-e \
    --to=stefani@seibold.net \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.baluta@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hagen@jauu.net \
    --cc=jj@chaosbits.net \
    --cc=jochen@jochen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shemminger@vyatta.com \
    --cc=torvalds@linux-foundation.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.