On 12/7/2017 1:52 PM, Alexander Duyck wrote:
The reads/writes themselves should be cheap. These kind of things only
get to be really expensive when you start looking at adding delays in
between the writes/reads polling on things. As long as we aren't
waiting milliseconds on things you can write/
On Thu, Dec 7, 2017 at 10:47 AM, Shannon Nelson
wrote:
> On 12/7/2017 9:16 AM, Alexander Duyck wrote:
>>
>> On Wed, Dec 6, 2017 at 9:43 PM, Shannon Nelson
>> wrote:
>>>
>>> On 12/5/2017 9:30 AM, Alexander Duyck wrote:
On Mon, Dec 4, 2017 at 9:35 PM, Shannon Nelson
wrote:
On 12/7/2017 9:16 AM, Alexander Duyck wrote:
On Wed, Dec 6, 2017 at 9:43 PM, Shannon Nelson
wrote:
On 12/5/2017 9:30 AM, Alexander Duyck wrote:
On Mon, Dec 4, 2017 at 9:35 PM, Shannon Nelson
wrote:
On a chip reset most of the table contents are lost, so must be
+ /* reload the I
On Wed, Dec 6, 2017 at 9:43 PM, Shannon Nelson
wrote:
> On 12/5/2017 9:30 AM, Alexander Duyck wrote:
>>
>> On Mon, Dec 4, 2017 at 9:35 PM, Shannon Nelson
>> wrote:
>>>
>>> On a chip reset most of the table contents are lost, so must be
>>> restored. This scans the driver's ipsec tables and resto
On 12/5/2017 9:30 AM, Alexander Duyck wrote:
On Mon, Dec 4, 2017 at 9:35 PM, Shannon Nelson
wrote:
On a chip reset most of the table contents are lost, so must be
restored. This scans the driver's ipsec tables and restores both
the filled and empty table slots to their pre-reset values.
Signe
On Mon, Dec 4, 2017 at 9:35 PM, Shannon Nelson
wrote:
> On a chip reset most of the table contents are lost, so must be
> restored. This scans the driver's ipsec tables and restores both
> the filled and empty table slots to their pre-reset values.
>
> Signed-off-by: Shannon Nelson
> ---
> driv
