> searching in ip_masq_m_tab and ip_masq_s_tab where we must remove 1
> entry from 130000 => we must compare data for 65000 average per
> second (expect newly created connections in top of list followed by
> old connections, i.e. 65000-130000).
Would making the masq lists doubly-linked be too hideous to
contemplate? It would eliminate searching the list in
ip_masq_unhash(), and there's minimal impact on ip_masq_hash() if it
always inserts at the head of the list.
> - remove entry (slow - search 65000 entries)
Unhash for masq_expire() doesn't need to be fast since nothing is
waiting for it to complete, but ip_masq_unhash() gets called from
a few places in packet processing as well, so making it faster would
be a good thing.
-- John Hardin KA7OHZ jhardin@wolfenet.com pgpk -a finger://gonzo.wolfenet.com/jhardin PGP key ID: 0x41EA94F5 PGP key fingerprint: A3 0C 5B C2 EF 0D 2C E5 E9 BF C8 33 A7 A9 CE 76 ----------------------------------------------------------------------- In the Lion the Mighty Lion the Zebra sleeps tonight... Dee de-ee-ee-ee-ee de de de we um umma way! ----------------------------------------------------------------------- Today: Crusade: the Babylon Project
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/