| 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@davemloft.net> |
| References: | <20050606115939.GA399@gondor.apana.org.au> <20050606120914.GA8317@infradead.org> <20050606124043.GA625@gondor.apana.org.au> <20050606.154653.64001264.davem@davemloft.net> |
| 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 fragments. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt |
| Previous by Date: | Re: [PATCH] tg3: Fix link failure in 5701, Grant Grundler |
|---|---|
| Next by Date: | Re: [RFC] Replace scatterlist with crypto_frag, Jeff Garzik |
| Previous by Thread: | Re: [RFC] Replace scatterlist with crypto_frag, David S. Miller |
| Next by Thread: | Re: [RFC] Replace scatterlist with crypto_frag, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |