From: jim owens <owens6336@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH V3 00/18] Btrfs: Direct I/O read rebased.
Date: Sun, 21 Mar 2010 23:17:26 -0400 [thread overview]
Message-ID: <4BA6E146.10709@gmail.com> (raw)
Here is the complete direct I/O read patch series
rebased onto the current btrfs-unstable and tested
against 2.6.33.
I have not done clean up of the diocb/extcb and did not
simplify the user memory handling yet.
There still is a problem with the wakeup of the submit
thread in btrfs_dio_wait(). With fsx on a 2-core x86-64
it will eventually hang, as in within 2 hours. Either
I am missing the wakeup or miscounting the done state
and going back to sleep with all I/O finished.
jim
reply other threads:[~2010-03-22 3:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BA6E146.10709@gmail.com \
--to=owens6336@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).