netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] [NET]: Supporting UDP-Lite (RFC 3828) in Linux
Date: Mon, 13 Nov 2006 07:56:52 +0000	[thread overview]
Message-ID: <200611130756.52728@strip-the-willow> (raw)
In-Reply-To: <20061110093715.0aadd791@freekitty>

Quoting Stephen Hemminger:
|  On Fri, 10 Nov 2006 16:09:20 +0000
|  Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
|  
|  > [NET/IPv4]: Support for the UDP-Lite protocol (RFC 3828)
|  > 
|  > This adds support for UDP-Lite to the IPv4 stack, provided as an extension
|  > to the existing UDPv4 code:
|  > 	* generic routines are all located in net/ipv4/udp.c
|  > 	* UDP-Lite specific routines are in net/ipv4/udplite.c
|  > 	* MIB/statistics support in /proc/net/snmp and /proc/net/udplite
|  > 	* shared API with extensions for partial checksum coverage
|  > 	* consolidation of shared code
|  > 
|  > 
|  
|  This code is does too much inlining (like existing network code).
|  Should it be made configurable?
That is a late question for a patch which has been in a RFC phase for several months.
This patch had been submitted repeatedly for RFC between middle of September ... end 
of October.

It used to be configurable and it also used to be much more bloated:

 	``The in-lining is a feature, not a bug!''

Reason: If you look at udplite.c (which is, despite #including, a fully self-contained
        protocol module), the inline functions all call generic code from udp.c. If you
        then look back at udp.c, you see that UDP almost does the same. What you have here
        is two protocols for the price of one; the inlines work as wrappers for both UDP
        and UDP-Lite. And considerable amount of extracting and minimising went into making
        it that way.

Before: The patch used to be separate and was an `enormous mass of code reduplication'. 
        Imagine udp.c reduplicated and modified to run UDP-Lite: then you have two highly
        similar code files, over 90% of code reduplication (bad ... very bad).

Is there someone else supporting `make UDP-Lite' configurable -- in the end I am being asked
to re-implement a feature I was asked to remove a couple of months ago. It is not a problem
to do this, but this code has cost a lot of work and I would like to finally see it in 2.6.20.

Gerrit

  parent reply	other threads:[~2006-11-13  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 16:09 [PATCH 1/3] [NET]: Supporting UDP-Lite (RFC 3828) in Linux Gerrit Renker
2006-11-10 17:37 ` Stephen Hemminger
2006-11-10 22:38   ` David Miller
2006-11-10 22:48     ` Stephen Hemminger
2006-11-13  7:43     ` Gerrit Renker
2006-11-13  7:56   ` Gerrit Renker [this message]
2006-11-10 22:38 ` David Miller
2006-11-13  7:34   ` Gerrit Renker
2006-11-13  7:46     ` David Miller
     [not found]     ` <200611130809.34613@strip-the-willow>
     [not found]       ` <20061113.001615.74565996.davem@davemloft.net>
2006-11-13  8:32         ` Gerrit Renker
2006-11-13  9:28           ` David Miller

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=200611130756.52728@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).