From: Stephen Hemminger <shemminger@osdl.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: [IPROUTE 00/03]: Increase number of possible routing tables
Date: Thu, 10 Aug 2006 16:13:20 -0700 [thread overview]
Message-ID: <20060810161320.168674c8@localhost.localdomain> (raw)
In-Reply-To: <20060810221447.9060.5563.sendpatchset@localhost.localdomain>
On Fri, 11 Aug 2006 00:14:47 +0200 (MEST)
Patrick McHardy <kaber@trash.net> wrote:
> These patches add support for a larger number of routing tables to iproute
> and are needed for the patches doing the same for the kernel I just sent.
> They apply on top of the "[IPROUTE]: Support IPv6 routing table filter" patch.
>
> Please apply, thanks.
>
>
> include/linux/rtnetlink.h | 4 -
> include/rt_names.h | 2
> ip/ip_common.h | 8 +++
> ip/iproute.c | 63 ++++++++++++++++------------
> ip/iprule.c | 14 +++++-
> lib/rt_names.c | 100 ++++++++++++++++++++++++++++++++++------------
> 6 files changed, 133 insertions(+), 58 deletions(-)
>
> Patrick McHardy:
> [IPROUTE]: Preparation for 32 bit table IDs
> [IPROUTE]: Use hash for routing table name cache
> [IPROUTE]: Add support for larger number of routing tables
Applied thanks. Let me know when your done, it has been too long
since a real release of iproute2. I'll roll one as soon as the flow subsides.
next prev parent reply other threads:[~2006-08-10 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 22:14 [IPROUTE 00/03]: Increase number of possible routing tables Patrick McHardy
2006-08-10 22:14 ` [IPROUTE 01/03]: Preparation for 32 bit table IDs Patrick McHardy
2006-08-10 22:14 ` [IPROUTE 02/03]: Use hash for routing table name cache Patrick McHardy
2006-08-10 22:14 ` [IPROUTE 03/03]: Add support for larger number of routing tables Patrick McHardy
2006-08-10 23:13 ` Stephen Hemminger [this message]
2006-08-10 23:23 ` [IPROUTE 00/03]: Increase number of possible " Patrick McHardy
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=20060810161320.168674c8@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=kaber@trash.net \
--cc=netdev@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 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.