Messages in this thread | | | Date | Sat, 9 Aug 2003 10:39:10 -0700 | From | "David S. Miller" <> | Subject | Re: [RFC][PATCH] Make cryptoapi non-optional? |
| |
On Sat, 9 Aug 2003 09:05:42 -0500 Matt Mackall <mpm@selenic.com> wrote:
> All of which is a big waste of time if the answer to "is making > cryptoapi mandatory ok?" is no. So before embarking on the hard part, > I thought I'd ask the hard question.
I'm personally OK with it, and in fact I talked about this with James (converting random.c over to the crypto API and the implications) early on while we were first working on the crypto kernel bits.
But I fear some embedded folks might bark. Especially if the resulting code size is significantly larger.
We could make it a config option CONFIG_RANDOM_CRYPTOAPI.
All of this analysis nearly requires a working implementation so someone can do a code-size and performance comparison between the two cases. I know this is what you're trying to avoid, having to code up what might be just thrown away :(
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |