[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [Bcache v13 07/16] Closures
- From: Alan Cox <alan lxorguk ukuu org uk>
- To: Kent Overstreet <koverstreet google com>
- Cc: Tejun Heo <tj kernel org>, linux-bcache vger kernel org, agk redhat com, linux-kernel vger kernel org, dm-devel redhat com
- Subject: Re: [dm-devel] [Bcache v13 07/16] Closures
- Date: Fri, 18 May 2012 11:02:47 +0100
> Well, I can definitely understand your reservations about the code; it's
> strange and foreign and complicated. But having beaten my head against
> the various problems and difficulties inherent in asynchronous
> programming for years - well, having found a way to make it sane to me
> it'd be madness to go back.
I think its more of a different paradigm than complicated. The big
question I'd have to ask is how does it fit with hard real time. That is
a big issue given the gradual merging and getting of "hard" real time
into the kernel proper.
In some ways it's not that strange either. A look at what happens on some
of our kref handling in drivers is very similar but hardcoded.
Is the handling of priority inversion within closures a well understood
and solved problem ?
Alan
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]