All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: lkml@einar-lueck.de
Cc: elueck@de.ibm.com, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/ipv4 for Source VIPA support, kernel BK Head
Date: Thu, 2 Sep 2004 13:50:23 -0700	[thread overview]
Message-ID: <20040902135023.1cacf608.davem@davemloft.net> (raw)
In-Reply-To: <200409021451.55318.elueck@de.ibm.com>

On Thu, 2 Sep 2004 14:51:55 +0200
Einar Lueck <elueck@de.ibm.com> wrote:

> On Donnerstag, 2. September 2004 13:24 Alan Cox wrote:
> > You've failed as far as I can see to explain why NAT doesn't do the
> > right thing in this case. I don't care whether the customers like it, I
> > care whether it works. If it works then we don't need to add junk to the
> > kernel. If it works but is hard to configure then its an opportunity to
> > write a nice tool to manage it.
> I am sorry: I failed to point out that NAT does the job!
> 
> We think that the the proposed patch, that is a really small one,
> introduces a facility that works well for existing operating systems 
> and is desired by customers. Consequently, it enriches the kernel with
> a concept that has already proven its value.

We never add patches that duplicate existing functionality just to
make it somehow "easier" for the user.  That's a job for scripts
and good tools, that make use of existing kernel facilities.

Alan is saying you can hide whatever complexity you claim exists via
tools, without any kernel modifications.  If you continue to ignore
that part of the discussion, it seems likely we will just the same
ignore your patch.

I, frankly, see no reason at all to even remotely consider your patch.
Furthermore, you'll get more discussion by bringing this up in the proper
place to propose such networking changes (netdev@oss.sgi.com).


  reply	other threads:[~2004-09-02 20:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 12:01 [PATCH] net/ipv4 for Source VIPA support, kernel BK Head Einar Lueck
2004-09-02 11:05 ` Alan Cox
2004-09-02 12:20   ` Einar Lueck
2004-09-02 11:24     ` Alan Cox
2004-09-02 12:51       ` Einar Lueck
2004-09-02 20:50         ` David S. Miller [this message]
2004-09-02 13:13 ` Bill Rugolsky Jr.
  -- strict thread matches above, loose matches on Subject: below --
2004-09-01 12:41 Einar Lueck
2004-09-01 12:25 ` Alan Cox
2004-09-02 16:22 ` Paul Jakma
2004-09-02 16:58   ` Einar Lueck
2004-09-02 20:59     ` Paul Jakma
2004-09-03  8:07       ` Einar Lueck
2004-09-03 16:53         ` Paul Jakma
2004-09-06  7:50           ` Einar Lueck
2004-09-06  7:57             ` Paul Jakma
2004-09-07 15:34         ` Herbert Poetzl
2004-09-05 23:02   ` Daniel Roesen
2004-09-06  3:22     ` David S. 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=20040902135023.1cacf608.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=elueck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@einar-lueck.de \
    /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.