All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/5] NET Improve layering of structs dst_entry/rtable/rt6_info/dn_route to get less dcache footprint
Date: Thu, 08 Feb 2007 22:32:10 +0100	[thread overview]
Message-ID: <45CB96DA.20400@cosmosbay.com> (raw)
In-Reply-To: <20070207.165213.98418769.davem@davemloft.net>

Hi David

Large routers/servers spend lot of CPU time in route cache lookups. This is 
because each item lookup uses two cache lines : the next pointer is at the 
begining of item, but keys are far away from this pointer.

Furthermore, the u unions declared in struct rtable, rt6_info and dn_route are 
imho quite ugly (forcing next pointer be at null offset)

This patch try to cleanup the layering and try to put the 'next' pointer near 
the fields used at lookup time (in ip_route_input() for example)

I prepared the following five patches :

[PATCH 1/5] : Introduce union in struct dst_entry, to prepare patches 2,3,4
[PATCH 2/5] : Convert ipv4 route to use the new dst_entry 'next' pointer
[PATCH 3/5] : Convert ipv6 route to use the new dst_entry 'next' pointer
[PATCH 4/5] : Convert decnet route to use the new dst_entry 'next' pointer
[PATCH 5/5] : Reorder fields of struct dst_entry

Thank you
Eric Dumazet

  reply	other threads:[~2007-02-08 21:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  0:42 Fw: [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 2) Shinta Sugimoto
2007-02-08  0:52 ` David Miller
2007-02-08 21:32   ` Eric Dumazet [this message]
2007-02-10  1:31     ` [PATCH 0/5] NET Improve layering of structs dst_entry/rtable/rt6_info/dn_route to get less dcache footprint David Miller
2007-02-10  8:17       ` Eric Dumazet
2007-02-08 21:33   ` [PATCH 1/5] NET : Introduce union in struct dst_entry to hold 'next' pointer Eric Dumazet

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=45CB96DA.20400@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=davem@davemloft.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.