netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Make xfrm subsystem optional
Date: Sat, 14 Jun 2003 02:38:43 -0700 (PDT)	[thread overview]
Message-ID: <20030614.023843.78709528.davem@redhat.com> (raw)
In-Reply-To: <20030614093630.GB16993@wotan.suse.de>

   From: Andi Kleen <ak@suse.de>
   Date: Sat, 14 Jun 2003 11:36:30 +0200

   Also when you do use it generically you will hopefully
   discard some old code (like the rt cache?) which may make
   up for the additional bloat. But until that happens having
   both even when not needed doesn't make too much sense.
   
The rtcache will likely be retained as a flow cache lookup
miss handler even once we use the flowcache for all lookups.

Actually, that entire area is in flux, I still do not know the
fate of the rtcache even without the flow cache :)

   > How about working on making the xfrm layer more lean instead? :)
   
   My last proposal for this (using hlists in the hash tables) was 
   rejected, so I don't see much chance to do this.

Because hlists cannot retain the behavior we need, specifically
because we need the ability to add to the tail.

If it's some in-kernel-image table, why not dynamically allocate the
table in question?

  reply	other threads:[~2003-06-14  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14  9:16 [PATCH] Make xfrm subsystem optional Andi Kleen
2003-06-14  9:27 ` David S. Miller
2003-06-14  9:36   ` Andi Kleen
2003-06-14  9:38     ` David S. Miller [this message]
2003-06-14 10:18       ` Andi Kleen
2003-06-14 11:26         ` David S. Miller
2003-06-14 18:32           ` Andi Kleen
2003-06-14 18:49             ` decorum John S. Denker
2003-06-14 22:02               ` decorum Ralph Doncaster
2003-06-15  3:04                 ` decorum David S. Miller
2003-06-15  3:03             ` [PATCH] Make xfrm subsystem optional David S. Miller
2003-06-15  8:08               ` Andi Kleen

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=20030614.023843.78709528.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@suse.de \
    --cc=netdev@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).