From: Jens Axboe <axboe@kernel.dk>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Justin TerAvest <teravest@google.com>,
Chad Talbott <ctalbott@google.com>,
Nauman Rafique <nauman@google.com>,
Divyesh Shah <dpshah@google.com>,
lkml <linux-kernel@vger.kernel.org>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Corrado Zoccolo <czoccolo@gmail.com>
Subject: Re: RFC: default group_isolation to 1, remove option
Date: Mon, 07 Mar 2011 21:36:52 +0100 [thread overview]
Message-ID: <4D7541E4.1000502@kernel.dk> (raw)
In-Reply-To: <20110307203420.GJ9540@redhat.com>
On 2011-03-07 21:34, Vivek Goyal wrote:
> One side affect of limitless bio queueing is an AIO process can queue
> up lots of bios in a group and if one tries to kill the process, it
> waits for all the IOs to finish and can take up a very long time
> depending on throttling limits of the group.
But I doubt this is a problem, really. Sure you could queue tons of IO
with aio if you really wanted, but aio does maintain er per-system
limit. So it's not infinite. The fact that waiting for pending aios can
take a while if you ctrl-c or kill the process is not a real worry,
imho.
--
Jens Axboe
prev parent reply other threads:[~2011-03-07 20:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 0:19 RFC: default group_isolation to 1, remove option Justin TerAvest
2011-03-01 14:20 ` Vivek Goyal
2011-03-01 18:44 ` Justin TerAvest
2011-03-02 21:28 ` Vivek Goyal
2011-03-06 16:06 ` Andrea Righi
2011-03-03 3:45 ` Jens Axboe
2011-03-03 15:30 ` Per iocontext request descriptor limits (Was: Re: RFC: default group_isolation to 1, remove option) Vivek Goyal
2011-03-03 15:44 ` Jens Axboe
2011-03-03 16:57 ` Vivek Goyal
2011-03-03 18:03 ` Vivek Goyal
2011-03-04 11:01 ` Jens Axboe
2011-03-04 21:31 ` Vivek Goyal
2011-03-04 21:34 ` Jens Axboe
2011-03-07 18:20 ` RFC: default group_isolation to 1, remove option Justin TerAvest
2011-03-07 19:39 ` Jens Axboe
2011-03-07 20:24 ` Vivek Goyal
2011-03-07 20:32 ` Jens Axboe
2011-03-07 20:46 ` Vivek Goyal
2011-03-07 20:47 ` Jens Axboe
2011-03-07 23:41 ` Justin TerAvest
2011-03-08 0:05 ` Vivek Goyal
2011-03-07 20:34 ` Vivek Goyal
2011-03-07 20:36 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7541E4.1000502@kernel.dk \
--to=axboe@kernel.dk \
--cc=ctalbott@google.com \
--cc=czoccolo@gmail.com \
--cc=dpshah@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nauman@google.com \
--cc=teravest@google.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).