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 04:26:36 -0700 (PDT) [thread overview]
Message-ID: <20030614.042636.74749587.davem@redhat.com> (raw)
In-Reply-To: <20030614101851.GA24170@wotan.suse.de>
From: Andi Kleen <ak@suse.de>
Date: Sat, 14 Jun 2003 12:18:51 +0200
Allocating it at first lookup would be racy (would need a nasty
spinlock at least). It may be possible at first policy setup, but
it's not guaranteed you can still get two 32K continuous areas. You
could fall back to vmalloc I guess.
Andi, you're getting rediculious. Add a xfrm_whatever_init() call
and allocate the table there.
Oh, I see, we do that already... end of discussion I guess.
next prev parent reply other threads:[~2003-06-14 11:26 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
2003-06-14 10:18 ` Andi Kleen
2003-06-14 11:26 ` David S. Miller [this message]
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.042636.74749587.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).