From: Michael Tokarev <mjt@tls.msk.ru>
To: Patrick McHardy <kaber@trash.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org, patrick@tykepenguin.com
Subject: Re: [NET 00/06]: Increase number of possible routing tables
Date: Fri, 11 Aug 2006 10:39:19 +0400 [thread overview]
Message-ID: <44DC2617.7020200@tls.msk.ru> (raw)
In-Reply-To: <20060810192957.14867.71965.sendpatchset@localhost.localdomain>
Patrick McHardy wrote:
> These are the updated patches (against net-2.6.19) to increase the number
> of possible routing tables to 2^32. They basically consist of four parts:
>
> - Use u32 for routing table IDs everywhere inside the kernel
Just out of curiocity: why current limit of 2^31 isn't sufficient?
Or am I missing the point?
Thanks.
/mjt
next prev parent reply other threads:[~2006-08-11 6:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 19:29 [NET 00/06]: Increase number of possible routing tables Patrick McHardy
2006-08-10 19:29 ` [NET 01/06]: Use u32 for routing table IDs Patrick McHardy
2006-08-11 6:08 ` David Miller
2006-08-10 19:30 ` [NET 02/06]: Introduce RTA_TABLE/FRA_TABLE attributes Patrick McHardy
2006-08-11 6:09 ` David Miller
2006-08-11 7:02 ` Michael Tokarev
2006-08-11 7:33 ` David Miller
2006-08-10 19:30 ` [IPV4 03/06]: Increase number of possible routing tables to 2^32 Patrick McHardy
2006-08-11 6:10 ` David Miller
2006-08-10 19:30 ` [IPV6 04/06]: " Patrick McHardy
2006-08-11 6:11 ` David Miller
2006-08-10 19:30 ` [DECNET 05/06]: " Patrick McHardy
2006-08-11 6:11 ` David Miller
2006-08-10 19:30 ` [NET 06/06]: Increate RT_TABLE_MAX " Patrick McHardy
2006-08-11 6:12 ` David Miller
2006-08-11 6:39 ` Michael Tokarev [this message]
2006-08-11 6:44 ` [NET 00/06]: Increase number of possible routing tables David Miller
2006-08-11 6:56 ` Michael Tokarev
2006-08-11 9:48 ` Thomas Graf
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=44DC2617.7020200@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=patrick@tykepenguin.com \
/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.