All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Gallati <lartc@draxinusom.ch>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] large routing table
Date: Wed, 31 Mar 2004 21:24:21 +0000	[thread overview]
Message-ID: <406B3705.404@draxinusom.ch> (raw)
In-Reply-To: <4069FB34.6000507@draxinusom.ch>

Hello,

> I know that routes can be cached what should help, but
> here we are talking about tc u32 filter, which can not be cached as I know
> without hierarchy it is not posible to decrease amount of testing
> 
> but the interesting idea is to use route for packet classification
> or it can be simulated with netfilters connmark module.
> then amount of test to be done will be more than half of active connections
> number.

I think I will do exactly that. I was thinking somewhere along the lines 
that the routing infrastructure would be the best place to do it, but 
the connection tracker of netfilter is quite a bonus since it keeps 
state and so does minimize the times when I need to walk my 
classification tree to find out how to treat the connection.

Also I don't really need to route, since all the traffic goes out of the 
same interface anyway.

Thanks for all the hints !

CU

René


> 
> ----- Original Message ----- 
> From: <alex@pilosoft.com>
> To: "Roy" <roy@xxx.lt>
> Cc: <lartc@mailman.ds9a.nl>
> Sent: Wednesday, March 31, 2004 4:06 AM
> Subject: Re: [LARTC] large routing table
> 
> 
> 
>>On Wed, 31 Mar 2004, Roy wrote:
>>
>>
>>>100kbytes of prefixes is not so good , hashing does not mean
>>
>>anything
>>
>>>faster when checking ip you will need to test 4 bytes in any
>>
>>way, since
>>
>>>hash is usualy 32 bit too. this can help on very complex rules
>>
>>only. so
>>
>>>if you pump 100 kbytes of prefixes this is probably 7000
>>
>>addreses so on
>>
>>>each packet 7000 tests will be done.
>>
>>Incorrect. Linux route lookup is crappy, but not THAT crappy.
>>Route-cache somewhat helps too.
>>
>>-alex
>>
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-03-31 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 22:56 [LARTC] large routing table Rene Gallati
2004-03-31  1:06 ` alex
2004-03-31  1:25 ` alex
2004-03-31  1:26 ` Roy
2004-03-31  1:45 ` Roy
2004-03-31  9:50 ` Jeroen Vriesman
2004-03-31 10:26 ` Jeroen Vriesman
2004-03-31 21:01 ` Rene Gallati
2004-03-31 21:19 ` Rene Gallati
2004-03-31 21:24 ` Rene Gallati [this message]
2004-03-31 21:32 ` Rene Gallati
2004-03-31 21:41 ` Adrian Vasile

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=406B3705.404@draxinusom.ch \
    --to=lartc@draxinusom.ch \
    --cc=lartc@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.