public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cedric.hertault@v2plus.com
To: linux-kernel@vger.kernel.org
Subject: Re: [IPV4]: Increase number of possible routing tables to 2^32
Date: Thu, 15 Feb 2007 10:47:16 -0500	[thread overview]
Message-ID: <30987167.1171554435992.JavaMail.root@wombat.diezmil.com> (raw)
In-Reply-To: <200609240001.k8O01VL7008533@hera.kernel.org>

Hi,

It is all I need ! no more 256 routing tables limitation !. But now it is time for me to test it, but i am working on a kernel 2.6.9, do you think it will be good ?

Why do I need so much routing tables? I need more than 500 routing tables because my Linux have to work with 500 VLANs !. Do you think that your patch will be integreted in the Linux kernel or it stays limited at 256?

A very happy kernel noob :)

Cedric Hertault

--
This message was sent on behalf of cedric.hertault@v2plus.com at openSubscriber.com
http://www.opensubscriber.com/message/linux-kernel@vger.kernel.org/4967197.html

           reply	other threads:[~2007-02-15 16:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200609240001.k8O01VL7008533@hera.kernel.org>]

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=30987167.1171554435992.JavaMail.root@wombat.diezmil.com \
    --to=cedric.hertault@v2plus.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox