public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zach.brown@oracle.com>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: linux-aio@kvack.org, Xavier Roche <roche+kml2@exalead.com>,
	linux-kernel@vger.kernel.org
Subject: Re: io_submit() taking a long time to return ?
Date: Thu, 13 Jul 2006 09:48:33 -0700	[thread overview]
Message-ID: <44B67961.4040600@oracle.com> (raw)
In-Reply-To: <5d96567b0607130932g7ba6cf0jfebdb0af9c933000@mail.gmail.com>


> what do u means by "sync block mapping " ?

To find out what blocks to issue async IO against the submission path
reads metadata from the file system that maps file regions to disk
blocks.  These metadata reads are synchronous and so can block the
submitting task.  The mappings tend to be cached, though, which is why
this doesn't seem to be a problem in practice.

- z

      reply	other threads:[~2006-07-13 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  6:51 io_submit() taking a long time to return ? Xavier Roche
2006-07-13 15:44 ` Zach Brown
2006-07-13 16:32   ` Raz Ben-Jehuda(caro)
2006-07-13 16:48     ` Zach Brown [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=44B67961.4040600@oracle.com \
    --to=zach.brown@oracle.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raziebe@gmail.com \
    --cc=roche+kml2@exalead.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