Re: [PATCH 0/9] v2 ipv4/ipv6 refcount conversions

2017-07-04 Thread David Miller
From: Elena Reshetova Date: Tue, 4 Jul 2017 09:34:53 +0300 > Changes in v2: > * rebase on top of net-next > * currently by default refcount_t = atomic_t (*) and uses all >atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled. >This is a

Re: [PATCH 0/9] v2 ipv4/ipv6 refcount conversions

2017-07-04 Thread David Miller
From: Elena Reshetova Date: Tue, 4 Jul 2017 09:34:53 +0300 > Changes in v2: > * rebase on top of net-next > * currently by default refcount_t = atomic_t (*) and uses all >atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled. >This is a compromise for the systems that are

[PATCH 0/9] v2 ipv4/ipv6 refcount conversions

2017-07-04 Thread Elena Reshetova
Changes in v2: * rebase on top of net-next * currently by default refcount_t = atomic_t (*) and uses all atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled. This is a compromise for the systems that are critical on performance (such as net) and cannot accept even slight

[PATCH 0/9] v2 ipv4/ipv6 refcount conversions

2017-07-04 Thread Elena Reshetova
Changes in v2: * rebase on top of net-next * currently by default refcount_t = atomic_t (*) and uses all atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled. This is a compromise for the systems that are critical on performance (such as net) and cannot accept even slight