| To: | ak@xxxxxxx |
|---|---|
| Subject: | Re: [PATCH] Make xfrm subsystem optional |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sat, 14 Jun 2003 04:26:36 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20030614101851.GA24170@xxxxxxxxxxxxx> |
| References: | <20030614093630.GB16993@xxxxxxxxxxxxx> <20030614.023843.78709528.davem@xxxxxxxxxx> <20030614101851.GA24170@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Andi Kleen <ak@xxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Make xfrm subsystem optional, Andi Kleen |
|---|---|
| Next by Date: | Re: e1000 performance hack for ppc64 (Power4), Greg KH |
| Previous by Thread: | Re: [PATCH] Make xfrm subsystem optional, Andi Kleen |
| Next by Thread: | Re: [PATCH] Make xfrm subsystem optional, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |