On Thu, Feb 21, 2008 at 12:10:12PM +0300, Evgeniy Polyakov wrote: > > But req->nbytes should or should not correspond to number of bytes to be > encrypted? HIFN driver assumes so, it can be changed to run through > scatterlists (btw, how will it determine how many of them were > provided?) and get full size of the request from them, but I suspected > that req->nbytes should always be equal to number of bytes to be > encrypted by the driver, otherwise where to get that info from? Yes by the time the request gets to hifn req->nbytes would have been decremented by 12 bytes which means that it is now the exact amount of data that needs to be encrypted. However, if you follow the scatterlist then you will see more data available which is normal. 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 - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
