On 4/13/13 10:42 AM, weijin wrote:
On 04/13/2013 07:27 AM, James Peach wrote:
On Apr 11, 2013, at 7:25 PM, weijin wrote:
after changed to Linux Native AIO, the AIO callback happened in the same
thread, that means all subsequent operations of vol init will be also
happened in only one thread.
On 04/13/2013 07:27 AM, James Peach wrote:
On Apr 11, 2013, at 7:25 PM, weijin wrote:
after changed to Linux Native AIO, the AIO callback happened in the same
thread, that means all subsequent operations of vol init will be also happened
in only one thread.
Why is this? Is it due to the way
On Apr 11, 2013, at 7:25 PM, weijin wrote:
> after changed to Linux Native AIO, the AIO callback happened in the same
> thread, that means all subsequent operations of vol init will be also
> happened in only one thread.
Why is this? Is it due to the way your change works or the way Linux AIO
On 4/11/13 8:25 PM, weijin wrote:
after changed to Linux Native AIO, the AIO callback happened in the same
thread, that means all subsequent operations of vol init will be also
happened in only one thread.
But the previous aio can callback in any ET_CALL thread, so in most case
the vol init ope
after changed to Linux Native AIO, the AIO callback happened in the same
thread, that means all subsequent operations of vol init will be also
happened in only one thread.
But the previous aio can callback in any ET_CALL thread, so in most case
the vol init operations can spread to many thread.
Hi Weijin,
I'm looking at the Linux AOI changes, and there is one place where you lift the
Vol::init out into a VolInit continuation. This change doesn't seem specific to
Linux AIO ... can you explain why it's being done? Is it safe to do it when
Linux AIO is not enabled?
thanks,
James
