netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "James R. Leu" <jleu@mindspring.com>
To: netdev@oss.sgi.com
Cc: Mehulkumar J Patel <mehul.patel@in.ibm.com>,
	olh@suse.de, aprasad@in.ibm.com, kaena@us.ibm.com,
	mfrueh@suse.de, olaf@suse.de, davem@redhat.com
Subject: Re: Linux kernel updates and ip_crossover patch
Date: Thu, 30 Oct 2003 12:17:30 -0600	[thread overview]
Message-ID: <20031030181654.GA1474@mindspring.com> (raw)
In-Reply-To: <20031030095312.6ef82ff7.davem@redhat.com>

I agree with David that this patch has a very narrow scope.  I think a
more generic solution for a virtualized IP stack would be used by many more
people, and still solve this specific problem.

I have a patch for 'virtualizing' the IPv4 stack for the 2.4 kernel
series.  I'm working on porting it to the 2.6 kernels and adding the
same functionality for IPv6.

If you're interested in checking out the 2.4 kernel patch you can get
the latest stable version from http://linux-vrf.sf.net/

That page also descibes howto get the most recent version from
my development tree.

-- 
James R. Leu
jleu@mindspring.com

On Thu, Oct 30, 2003 at 09:53:12AM -0800, David S. Miller wrote:
> On Thu, 30 Oct 2003 18:33:57 +0530
> Mehulkumar J Patel <mehul.patel@in.ibm.com> wrote:
> 
> > Basically we need IP CROSSOVER patch to be part of pseries kernel.
> 
> This is not how the Linux community works.  You don't say "hey, we
> _NEED_ this" and like magic it gets added to the Linux kernel.
> 
> Rather, it gets added because someone submits it and the community
> sees a need for the feature.
> 
> As networking maintainer what I see is that this feature is needed by
> and used by only a very small group of people for very specialized
> purposes.  Therefore there is no urgency to add this to the kernel
> sources any time soon.
> 
> You can continue whining, complaining about how much you personally
> _NEED_ the ip_crossover patch, but that isn't going to help you
> arrive at your goal.  Rather you should spend time explaining to
> the community what value it gives to them and why it would be useful
> to anything other than very specialized cases and uses.

  reply	other threads:[~2003-10-30 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 13:03 Linux kernel updates and ip_crossover patch Mehulkumar J Patel
2003-10-30 13:16 ` Matthias Fruehauf
2003-10-30 17:53 ` David S. Miller
2003-10-30 18:17   ` James R. Leu [this message]
2003-10-31  3:16 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2003-10-27 14:24 Mehulkumar J Patel
2003-10-27 16:16 ` Ben Greear
2003-10-27 16:34   ` Anil K Prasad

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=20031030181654.GA1474@mindspring.com \
    --to=jleu@mindspring.com \
    --cc=aprasad@in.ibm.com \
    --cc=davem@redhat.com \
    --cc=kaena@us.ibm.com \
    --cc=mehul.patel@in.ibm.com \
    --cc=mfrueh@suse.de \
    --cc=netdev@oss.sgi.com \
    --cc=olaf@suse.de \
    --cc=olh@suse.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 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).