Re: dst_output() inner loop.

On Fri, Apr 07, 2006 at 05:34:27AM +1000, Herbert Xu ([EMAIL PROTECTED]) wrote: > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > > > > I just wonder why stackable dst_output() was removed? > > It's part of the netfilter/xfrm change where this change (not really > a removal though) makes things much

Re: dst_output() inner loop.

Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > > I just wonder why stackable dst_output() was removed? It's part of the netfilter/xfrm change where this change (not really a removal though) makes things much easier. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~

Re: dst_output() inner loop.

On Fri, Apr 07, 2006 at 03:50:54AM +1000, Herbert Xu ([EMAIL PROTECTED]) wrote: > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > > > > This change removed stackable output processing, which was a good idea by > > design (and there are users outside the kernel, like asynchronous crypto > > processin

Re: dst_output() inner loop.

Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > > This change removed stackable output processing, which was a good idea by > design (and there are users outside the kernel, like asynchronous crypto > processing for IPsec). Is there any reason why you can't do async crypto with the existing framewo