From: jim owens <jowens@hp.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [RFC 00/12] btrfs core patches for direct I/O
Date: Mon, 04 Jan 2010 16:11:04 -0500 [thread overview]
Message-ID: <4B425968.4020308@hp.com> (raw)
As if a Monday after a long holiday was not bad enough... this series
has some simple patches in existing btrfs code that I want to make for
btrfs directio code.
The RESEND patches 1-5 were sent to Chris in December because IMO
they have value without my directio code. You need them to apply
some of the subsequent patches.
IMO patch 6 is also of value independent of direct I/O, it reduces
vmalloc use by 42K per worker, though we still use 268K per worker (ouch).
Patches 7 - 12 don't have value without direct I/O. I'm sending
them RFC as they can be understood by themselves, and they are much
simpler than the directio code that uses them. :)
Note - might as well explain this now as later when I send the big
mess of dio.c for review. The existing core code for pagecache
doesn't work for directio because the existing I/O routines depend
on peeking inside a struct page to get the valid btrfs inode info.
Sorry, no can do, we don't own that page. And rewriting the whole
pagecache I/O stack to eliminate dependence on struct page would
be too scary IMO.
FWIW, fsx didn't crash on this series.
jim
next reply other threads:[~2010-01-04 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 21:11 jim owens [this message]
2010-01-06 11:50 ` [RFC 00/12] btrfs core patches for direct I/O Andi Kleen
2010-01-06 18:53 ` jim owens
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=4B425968.4020308@hp.com \
--to=jowens@hp.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