From: William Lee Irwin III <wli@holomorphy.com>
To: Janet Morgan <janetmor@us.ibm.com>
Cc: akpm@digeo.com, suparna@in.ibm.com, bcrl@redhat.com,
linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch 2/2] Retry based aio read - filesystem read changes
Date: Mon, 31 Mar 2003 11:11:23 -0800 [thread overview]
Message-ID: <20030331191123.GB13178@holomorphy.com> (raw)
In-Reply-To: <3E8889B4.FB716506@us.ibm.com>
On Mon, Mar 31, 2003 at 10:32:20AM -0800, Janet Morgan wrote:
> 70% of all calls to schedule were from __lock_page:
> Based on the profile data, almost all calls to _lock_page were
> from do_generic_mapping_read (see filemap.c/Line 101 below).
> Suparna's patch already retries here.
Can you tell whether these are due to hash collisions or contention on
the same page?
If they're due to hash collisions, things could easily be done to help
(though they wouldn't guarantee not sleeping entirely they'd be good
for general performance).
-- wli
next prev parent reply other threads:[~2003-03-31 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 9:17 [RFC][Patch] Retry based aio read for filesystems Suparna Bhattacharya
2003-03-05 9:26 ` [Patch 1/2] Retry based aio read - core aio changes Suparna Bhattacharya
2003-03-14 13:23 ` Suparna Bhattacharya
2003-03-05 9:30 ` [Patch 2/2] Retry based aio read - filesystem read changes Suparna Bhattacharya
2003-03-05 10:42 ` Andrew Morton
2003-03-05 12:14 ` Suparna Bhattacharya
2003-03-31 18:32 ` Janet Morgan
2003-03-31 19:11 ` William Lee Irwin III [this message]
2003-03-31 19:16 ` Benjamin LaHaise
2003-03-31 19:07 ` Janet Morgan
2003-04-01 20:24 ` Benjamin LaHaise
2003-03-31 19:17 ` William Lee Irwin III
2003-03-31 19:25 ` Benjamin LaHaise
2003-04-07 3:51 ` Suparna Bhattacharya
2003-03-05 23:00 ` [RFC][Patch] Retry based aio read for filesystems Janet Morgan
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=20030331191123.GB13178@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=bcrl@redhat.com \
--cc=janetmor@us.ibm.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.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
Powered by JetHome