Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing tables,
these are the resulting patches.
The table IDs are changed to 32 bit values and are contained in a new netlink
routing attribute. For compatibility rtm_table in struct rtmsg can still be
used
Patrick McHardy wrote:
Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing tables,
these are the resulting patches.
I am seeing problems..though they could be with the way I'm using the tool
or pehaps I patched the kernel incorrectly.
I applied the 3
Ben Greear wrote:
Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing
tables, these are the resulting patches.
I am seeing problems..though they could be with the way I'm using the tool
or pehaps I patched the kernel incorrectly.
I applied the
Patrick McHardy wrote:
Ben Greear wrote:
Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing
tables, these are the resulting patches.
I am seeing problems..though they could be with the way I'm using the tool
or pehaps I patched the kernel
David Miller wrote:
Nice work Patrick.
You guys have a lot of time to flesh out any remaining issues and
failures, and then submit this for 2.6.19
Will do, I already expected to miss the deadline :)
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message
Ben Greear wrote:
With this patch applied everything is looking much better. I currently
have 400+ interfaces and one routing table per interface, and traffic
is passing as expected.
This is probably due to my own application polling interfaces for
stat updates...but I am seeing over 50%
Patrick McHardy wrote:
Ben Greear wrote:
With this patch applied everything is looking much better. I currently
have 400+ interfaces and one routing table per interface, and traffic
is passing as expected.
This is probably due to my own application polling interfaces for
stat updates...but I
I took on Ben's challenge to increase the number of possible routing tables,
these are the resulting patches.
The table IDs are changed to 32 bit values and are contained in a new netlink
routing attribute. For compatibility rtm_table in struct rtmsg can still be
used to access the first 255
Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing tables,
these are the resulting patches.
The table IDs are changed to 32 bit values and are contained in a new netlink
routing attribute. For compatibility rtm_table in struct rtmsg can still be
used
Patrick McHardy wrote:
Patrick McHardy wrote:
I took on Ben's challenge to increase the number of possible routing tables,
these are the resulting patches.
The table IDs are changed to 32 bit values and are contained in a new netlink
routing attribute. For compatibility rtm_table in struct
* Patrick McHardy [EMAIL PROTECTED] 2006-07-03 11:38
That wasn't entirely true either, its not inet_check_attr but
rtnetlink_rcv_message that aborts, and it does this on all
kernels. Somehow I thought unknown attributes were usually
ignored ..
This only applies to the first level of rtnetlink
Thomas Graf wrote:
* Patrick McHardy [EMAIL PROTECTED] 2006-07-03 11:38
That wasn't entirely true either, its not inet_check_attr but
rtnetlink_rcv_message that aborts, and it does this on all
kernels. Somehow I thought unknown attributes were usually
ignored ..
This only applies to the
* Patrick McHardy [EMAIL PROTECTED] 2006-07-03 13:36
They will as long as this feature isn't used, the RTA_TABLE
attribute is only added to the message when the table id
is 255. Worked fine during my tests, or are you refering
to something else?
Perfect, I said nothing :)
-
To unsubscribe
13 matches
Mail list logo
