From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: Avi Kivity <avi@scylladb.com>,
Christoph Hellwig <hch@infradead.org>,
Tomasz Grabiec <tgrabiec@scylladb.com>,
linux-xfs@vger.kernel.org
Subject: Re: io_submit() blocks for writes for substantial amount of time
Date: Tue, 19 Sep 2017 13:34:57 -0700 [thread overview]
Message-ID: <20170919203457.GB731@infradead.org> (raw)
In-Reply-To: <20170919173955.GB8139@dhcp-41-131.bos.redhat.com>
On Tue, Sep 19, 2017 at 01:39:55PM -0400, Brian Foster wrote:
> I'm not sure what difference it makes regardless. We still have to wait
> for an allocation to complete before we can issue an I/O. IIRC, the old
> defer allocs to a wq thing was more about saving stack space than
> providing async behavior.
At least in theory we could do the allocation from one workqueue
and submit the I/O from the next one. Except for the lack of modern
workqueues that is what the historic AIO code in RHEL2.1 (and maybe 3.0,
but I'm not sure did).
next prev parent reply other threads:[~2017-09-19 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 8:50 io_submit() blocks for writes for substantial amount of time Tomasz Grabiec
2017-09-19 12:27 ` Brian Foster
2017-09-19 14:58 ` Christoph Hellwig
2017-09-19 16:31 ` Avi Kivity
2017-09-19 17:39 ` Brian Foster
2017-09-19 20:34 ` Christoph Hellwig [this message]
2017-09-20 6:17 ` Avi Kivity
2017-09-20 10:50 ` Brian Foster
2017-09-20 11:11 ` Avi Kivity
2017-09-20 14:49 ` Christoph Hellwig
2017-09-23 18:23 ` Avi Kivity
2017-09-19 20:34 ` Christoph Hellwig
2017-09-20 6:14 ` Avi Kivity
2017-09-19 16:29 ` Avi Kivity
2017-09-19 17:38 ` Brian Foster
2017-09-19 17:53 ` Tomasz Grabiec
2017-09-19 23:38 ` Dave Chinner
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=20170919203457.GB731@infradead.org \
--to=hch@infradead.org \
--cc=avi@scylladb.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=tgrabiec@scylladb.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).