[Top] [All Lists]

Re: [RFC] Replace scatterlist with crypto_frag

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [RFC] Replace scatterlist with crypto_frag
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 7 Jun 2005 09:04:37 +1000
Cc: hch@xxxxxxxxxxxxx, jmorris@xxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20050606.154653.64001264.davem@xxxxxxxxxxxxx>
References: <20050606115939.GA399@xxxxxxxxxxxxxxxxxxx> <20050606120914.GA8317@xxxxxxxxxxxxx> <20050606124043.GA625@xxxxxxxxxxxxxxxxxxx> <20050606.154653.64001264.davem@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Jun 06, 2005 at 03:46:53PM -0700, David S. Miller wrote:
> So I guess I'm taking you a step backwards, I want to make
> skb_frag_struct a little bigger :-)  Ie. put the DMA mapping
> cookies into the skb_frag_struct, then a set of accessor
> macros like we have for scatterlist.  Well, in fact, it would
> become a scatterlist and therefore the only thing special
> about dma_map_skb() is that is maps a linear buffer via
> skb->data then the scatterlist in skb_shared_info(skb).

Bigger is better actually :) I'm now thinking of using the
memory occupied by the frags array for IPsec crypto operations.
So if it's bigger then it simply means that we can store more

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:

<Prev in Thread] Current Thread [Next in Thread>