| To: | Michal Ludvig <michal@xxxxxxxx> |
|---|---|
| Subject: | Re: Asynchronous crypto layer. |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 29 Oct 2004 11:11:14 -0400 |
| Cc: | Evgeniy Polyakov <johnpol@xxxxxxxxxxx>, netdev@xxxxxxxxxxx, cryptoapi@xxxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.61.0410291636020.25667@xxxxxxxxxxxxxxxx> |
| Organization: | jamalopolous |
| References: | <1099030958.4944.148.camel@uganda> <1099053738.1024.104.camel@xxxxxxxxxxxxxxxx> <20041029180652.113f0f6e@xxxxxxxxxxxxxxxxxxxx> <41824D9A.3070407@xxxxxxxx> <20041029183606.0b1a0538@xxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0410291636020.25667@xxxxxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 2004-10-29 at 10:53, Michal Ludvig wrote: > On Fri, 29 Oct 2004, Evgeniy Polyakov wrote: . > > > > If you compile this sources then you will still have old sync behaviour, > > IPsec and any other old-style application should be rewritten(like > > attached consumer.c) to use new asynchronous crypto layer features. > > This could be a bit of problem, because AFAIK the IPsec code doesn't allow > sleeping while processing the packet. It will likely need a bigger > rewrite. > I dont think its a big rewrite. cheers, jamal |
| Previous by Date: | Re: Asynchronous crypto layer., Evgeniy Polyakov |
|---|---|
| Next by Date: | Re: Asynchronous crypto layer., Evgeniy Polyakov |
| Previous by Thread: | Re: Asynchronous crypto layer., Evgeniy Polyakov |
| Next by Thread: | Re: Asynchronous crypto layer., jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |