Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-25 Thread Kent Overstreet
On Tue, Oct 25, 2016 at 09:55:21AM -0700, Eric Wheeler wrote: > Sure, I'll put it up with my -rc2 pull request to Jens. > > A couple of sanity checks (for my understanding at least): > > Why does bch_data_insert_start() no longer need to call > set_gc_sectors(op->c) now that

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-25 Thread Kent Overstreet
On Tue, Oct 25, 2016 at 09:55:21AM -0700, Eric Wheeler wrote: > Sure, I'll put it up with my -rc2 pull request to Jens. > > A couple of sanity checks (for my understanding at least): > > Why does bch_data_insert_start() no longer need to call > set_gc_sectors(op->c) now that

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-25 Thread Eric Wheeler
On Mon, 24 Oct 2016, Kent Overstreet wrote: > On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > > > Subject: sched: Better explain sleep/wakeup > > > From: Peter Zijlstra > > > Date: Wed Oct 19 15:45:27

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-25 Thread Eric Wheeler
On Mon, 24 Oct 2016, Kent Overstreet wrote: > On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > > > Subject: sched: Better explain sleep/wakeup > > > From: Peter Zijlstra > > > Date: Wed Oct 19 15:45:27 CEST 2016 > > > > > >

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-24 Thread Kent Overstreet
On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > Subject: sched: Better explain sleep/wakeup > > From: Peter Zijlstra > > Date: Wed Oct 19 15:45:27 CEST 2016 > > > > There were a few questions wrt how

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-24 Thread Kent Overstreet
On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > Subject: sched: Better explain sleep/wakeup > > From: Peter Zijlstra > > Date: Wed Oct 19 15:45:27 CEST 2016 > > > > There were a few questions wrt how sleep-wakeup works. Try and

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-24 Thread Kent Overstreet
On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > Subject: sched: Better explain sleep/wakeup > > From: Peter Zijlstra > > Date: Wed Oct 19 15:45:27 CEST 2016 > > > > There were a few questions wrt how

Re: ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-24 Thread Kent Overstreet
On Sun, Oct 23, 2016 at 06:57:26PM -0700, Davidlohr Bueso wrote: > On Wed, 19 Oct 2016, Peter Zijlstra wrote: > > > Subject: sched: Better explain sleep/wakeup > > From: Peter Zijlstra > > Date: Wed Oct 19 15:45:27 CEST 2016 > > > > There were a few questions wrt how sleep-wakeup works. Try and

ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-23 Thread Davidlohr Bueso
On Wed, 19 Oct 2016, Peter Zijlstra wrote: Subject: sched: Better explain sleep/wakeup From: Peter Zijlstra Date: Wed Oct 19 15:45:27 CEST 2016 There were a few questions wrt how sleep-wakeup works. Try and explain it more. Requested-by: Will Deacon

ciao set_task_state() (was Re: [PATCH -v4 6/8] locking/mutex: Restructure wait loop)

2016-10-23 Thread Davidlohr Bueso
On Wed, 19 Oct 2016, Peter Zijlstra wrote: Subject: sched: Better explain sleep/wakeup From: Peter Zijlstra Date: Wed Oct 19 15:45:27 CEST 2016 There were a few questions wrt how sleep-wakeup works. Try and explain it more. Requested-by: Will Deacon Signed-off-by: Peter Zijlstra (Intel)