From: jim owens <jowens@hp.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [RFC PATCH 00/01] Btrfs: add decompression code for direct I/O.
Date: Fri, 08 Jan 2010 12:10:18 -0500 [thread overview]
Message-ID: <4B4766FA.3090004@hp.com> (raw)
The following patch has the btrfs code changes/additions needed
to support reading compressed data in my directio code.
The code always runs in process context.
The callbacks:
int (*get_next_in)(struct bio_vec *vec, struct btrfs_inflate *icb);
int (*get_next_out)(struct bio_vec *vec, struct btrfs_inflate *icb);
track where we currently are in the compressed pages (get_next_in) and
uncompressed output user pages (get_next_out). (in) is always full pages,
(out) may be partial pages with offsets as the user input to direct I/O is
a set of memory vectors/lengths.
The callback:
void (*done_with_out)(struct bio_vec *vec, struct btrfs_inflate *icb);
is currently coded in directio as:
static void btrfs_dio_done_with_out(struct bio_vec *ovec,
struct btrfs_inflate *icb)
{
flush_dcache_page(ovec->bv_page);
if (!PageCompound(ovec->bv_page))
set_page_dirty_lock(ovec->bv_page);
page_cache_release(ovec->bv_page);
}
Again, this patch has no value without my directio code.
jim
reply other threads:[~2010-01-08 17:10 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=4B4766FA.3090004@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