RE: [PATCH 2/5] sched: convert signal_struct.sigcnt to refcount_t

2019-01-22 Thread Reshetova, Elena
> On Tue, Jan 22, 2019 at 09:11:42AM +, Reshetova, Elena wrote: > > Will you be able to take this and the other scheduler > > patch to whatever tree/path it should normally go to get eventually > > integrated? > > I've queeud them up. Thank you! Best Regards, Elena.

Re: [PATCH 2/5] sched: convert signal_struct.sigcnt to refcount_t

2019-01-22 Thread Peter Zijlstra
On Tue, Jan 22, 2019 at 09:11:42AM +, Reshetova, Elena wrote: > Will you be able to take this and the other scheduler > patch to whatever tree/path it should normally go to get eventually > integrated? I've queeud them up.

RE: [PATCH 2/5] sched: convert signal_struct.sigcnt to refcount_t

2019-01-22 Thread Reshetova, Elena
> On 01/18, Elena Reshetova wrote: > > > > For the signal_struct.sigcnt it might make a difference > > in following places: > > - put_signal_struct(): decrement in refcount_dec_and_test() only > >provides RELEASE ordering and control dependency on success > >vs. fully ordered atomic counte

Re: [PATCH 2/5] sched: convert signal_struct.sigcnt to refcount_t

2019-01-21 Thread Oleg Nesterov
On 01/18, Elena Reshetova wrote: > > For the signal_struct.sigcnt it might make a difference > in following places: > - put_signal_struct(): decrement in refcount_dec_and_test() only >provides RELEASE ordering and control dependency on success >vs. fully ordered atomic counterpart this is

[PATCH 2/5] sched: convert signal_struct.sigcnt to refcount_t

2019-01-18 Thread Elena Reshetova
atomic_t variables are currently used to implement reference counters with the following properties: - counter is initialized to 1 using atomic_set() - a resource is freed upon counter reaching zero - once counter reaches zero, its further increments aren't allowed - counter schema uses basi