Re: [PATCH] crypto: mask the crypto operations from totem packet size management

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/13/2012 4:45 PM, Fabio M. Di Nitto wrote:
> On 3/13/2012 4:26 PM, Steven Dake wrote:
>> On 03/13/2012 07:44 AM, Fabio M. Di Nitto wrote:
>>> From: "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx>
>>>
>>> totem doesn't need to understand what crypto does.
>>>
>>> totem needs to be able to tell crypto: "those are data, play with them"
>>> and crypto needs to return: "here are your scrambled data and the new size"
>>>
>>
>> crypto should take a max size (the network mtu) and ensure that what it
>> will only take an input that would product a maximum packet size.  This
>> is not trivial.

re-processing in my brain.. no this is too complex atm. We guarantee
that we don´t overflow that buffer by using a net_mtu that is
configured_mtu - crypto_header_size (as is now basically).

Fabio
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss



[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux