From: Omar Sandoval <osandov@osandov.com>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org, Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH 1/6] Btrfs: add extent buffer bitmap operations
Date: Tue, 1 Sep 2015 12:37:15 -0700 [thread overview]
Message-ID: <20150901193715.GA24255@huxley.DHCP.TheFacebook.com> (raw)
In-Reply-To: <55E5FBC2.7020809@fb.com>
On Tue, Sep 01, 2015 at 03:25:54PM -0400, Josef Bacik wrote:
> On 09/01/2015 03:01 PM, Omar Sandoval wrote:
> >From: Omar Sandoval <osandov@fb.com>
> >
> >These are going to be used for the free space tree bitmap items.
> >
> >Signed-off-by: Omar Sandoval <osandov@fb.com>
>
> Can we get sanity tests for these operations so we know they are properly
> unit tested?
>
No problem, I'll do that.
> >---
> > fs/btrfs/extent_io.c | 101 +++++++++++++++++++++++++++++++++++++++++++++++++++
> > fs/btrfs/extent_io.h | 6 +++
> > 2 files changed, 107 insertions(+)
> >
> >diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> >index 02d05817cbdf..649e3b4eeb1b 100644
> >--- a/fs/btrfs/extent_io.c
> >+++ b/fs/btrfs/extent_io.c
> >@@ -5475,6 +5475,107 @@ void copy_extent_buffer(struct extent_buffer *dst, struct extent_buffer *src,
> > }
> > }
> >
> >+/*
> >+ * The extent buffer bitmap operations are done with byte granularity because
> >+ * bitmap items are not guaranteed to be aligned to a word and therefore a
> >+ * single word in a bitmap may straddle two pages in the extent buffer.
> >+ */
> >+#define BIT_BYTE(nr) ((nr) / BITS_PER_BYTE)
> >+#define BYTE_MASK ((1 << BITS_PER_BYTE) - 1)
> >+#define BITMAP_FIRST_BYTE_MASK(start) \
> >+ ((BYTE_MASK << ((start) & (BITS_PER_BYTE - 1))) & BYTE_MASK)
> >+#define BITMAP_LAST_BYTE_MASK(nbits) \
> >+ (BYTE_MASK >> (-(nbits) & (BITS_PER_BYTE - 1)))
> >+
> >+int extent_buffer_test_bit(struct extent_buffer *eb, unsigned long start,
> >+ unsigned long nr)
> >+{
> >+ size_t offset;
> >+ char *kaddr;
> >+ struct page *page;
> >+ size_t byte_offset = BIT_BYTE(nr);
> >+ size_t start_offset = eb->start & ((u64)PAGE_CACHE_SIZE - 1);
> >+ unsigned long i = (start_offset + start + byte_offset) >> PAGE_CACHE_SHIFT;
> >+
> >+ offset = (start_offset + start + byte_offset) & (PAGE_CACHE_SIZE - 1);
> >+ page = eb->pages[i];
> >+ WARN_ON(!PageUptodate(page));
> >+ kaddr = page_address(page);
> >+ return 1U & (kaddr[offset] >> (nr & (BITS_PER_BYTE - 1)));
> >+}
> >+
> >+void extent_buffer_bitmap_set(struct extent_buffer *eb, unsigned long start,
> >+ unsigned long pos, unsigned long len)
> >+{
> >+ size_t offset;
> >+ char *kaddr;
> >+ struct page *page;
> >+ size_t byte_offset = BIT_BYTE(pos);
> >+ size_t start_offset = eb->start & ((u64)PAGE_CACHE_SIZE - 1);
> >+ unsigned long i = (start_offset + start + byte_offset) >> PAGE_CACHE_SHIFT;
> >+ const unsigned int size = pos + len;
> >+ int bits_to_set = BITS_PER_BYTE - (pos % BITS_PER_BYTE);
> >+ unsigned int mask_to_set = BITMAP_FIRST_BYTE_MASK(pos);
> >+
> >+ offset = (start_offset + start + byte_offset) & (PAGE_CACHE_SIZE - 1);
> >+ page = eb->pages[i];
> >+ WARN_ON(!PageUptodate(page));
> >+ kaddr = page_address(page);
> >+
> >+ while (len >= bits_to_set) {
> >+ kaddr[offset] |= mask_to_set;
> >+ len -= bits_to_set;
> >+ bits_to_set = BITS_PER_BYTE;
> >+ mask_to_set = ~0U;
> >+ if (++offset >= PAGE_CACHE_SIZE && len > 0) {
> >+ offset = 0;
> >+ page = eb->pages[++i];
> >+ WARN_ON(!PageUptodate(page));
> >+ kaddr = page_address(page);
> >+ }
> >+ }
> >+ if (len) {
> >+ mask_to_set &= BITMAP_LAST_BYTE_MASK(size);
> >+ kaddr[offset] |= mask_to_set;
> >+ }
> >+}
> >+
> >+void extent_buffer_bitmap_clear(struct extent_buffer *eb, unsigned long start,
> >+ unsigned long pos, unsigned long len)
> >+{
> >+ size_t offset;
> >+ char *kaddr;
> >+ struct page *page;
> >+ size_t byte_offset = BIT_BYTE(pos);
> >+ size_t start_offset = eb->start & ((u64)PAGE_CACHE_SIZE - 1);
> >+ unsigned long i = (start_offset + start + byte_offset) >> PAGE_CACHE_SHIFT;
> >+ const unsigned int size = pos + len;
> >+ int bits_to_clear = BITS_PER_BYTE - (pos % BITS_PER_BYTE);
> >+ unsigned int mask_to_clear = BITMAP_FIRST_BYTE_MASK(pos);
> >+
> >+ offset = (start_offset + start + byte_offset) & (PAGE_CACHE_SIZE - 1);
> >+ page = eb->pages[i];
> >+ WARN_ON(!PageUptodate(page));
> >+ kaddr = page_address(page);
> >+
>
> Abstract this offset finding logic to a helper function and then comment the
> hell out of it, I now have a migraine trying to figure out what is going on.
> Thanks,
>
> Josef
Will do, thanks.
--
Omar
next prev parent reply other threads:[~2015-09-01 19:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 19:01 [PATCH 0/6] free space B-tree Omar Sandoval
2015-09-01 19:01 ` [PATCH 1/6] Btrfs: add extent buffer bitmap operations Omar Sandoval
2015-09-01 19:25 ` Josef Bacik
2015-09-01 19:37 ` Omar Sandoval [this message]
2015-09-01 19:01 ` [PATCH 2/6] Btrfs: add helpers for read-only compat bits Omar Sandoval
2015-09-01 19:26 ` Josef Bacik
2015-09-01 19:01 ` [PATCH 3/6] Btrfs: introduce the free space B-tree on-disk format Omar Sandoval
2015-09-01 19:28 ` Josef Bacik
2015-09-01 19:05 ` [PATCH 5/6] Btrfs: wire up the free space tree to the extent tree Omar Sandoval
2015-09-01 19:48 ` Josef Bacik
2015-09-02 4:42 ` Omar Sandoval
2015-09-02 15:29 ` Josef Bacik
2015-09-01 19:05 ` [PATCH 6/6] Btrfs: add free space tree mount option Omar Sandoval
2015-09-01 19:49 ` Josef Bacik
2015-09-01 19:13 ` [PATCH 4/6] Btrfs: implement the free space B-tree Omar Sandoval
2015-09-01 19:44 ` Josef Bacik
2015-09-01 20:06 ` Omar Sandoval
2015-09-01 20:08 ` Josef Bacik
2015-09-01 19:17 ` [PATCH 0/6] " Omar Sandoval
2015-09-01 19:22 ` [PATCH 1/3] btrfs-progs: use calloc instead of malloc+memset for tree roots Omar Sandoval
2015-09-01 19:22 ` [PATCH 2/3] btrfs-progs: add basic awareness of the free space tree Omar Sandoval
2015-09-01 19:22 ` [PATCH 3/3] btrfs-progs: check the free space tree in btrfsck Omar Sandoval
2015-09-02 15:02 ` [PATCH 1/3] btrfs-progs: use calloc instead of malloc+memset for tree roots David Sterba
2015-09-03 19:44 ` [PATCH v2 0/9] free space B-tree Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 1/9] Btrfs: add extent buffer bitmap operations Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 2/9] Btrfs: add extent buffer bitmap sanity tests Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 3/9] Btrfs: add helpers for read-only compat bits Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 4/9] Btrfs: refactor caching_thread() Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 5/9] Btrfs: introduce the free space B-tree on-disk format Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 6/9] Btrfs: implement the free space B-tree Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 7/9] Btrfs: add free space tree sanity tests Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 8/9] Btrfs: wire up the free space tree to the extent tree Omar Sandoval
2015-09-04 5:56 ` Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 9/9] Btrfs: add free space tree mount option Omar Sandoval
2015-09-09 12:00 ` David Sterba
2015-09-11 0:52 ` Omar Sandoval
2015-09-04 1:29 ` [PATCH v2 0/9] free space B-tree Zhao Lei
2015-09-04 5:43 ` Omar Sandoval
2015-09-11 1:21 ` Qu Wenruo
2015-09-11 3:48 ` Omar Sandoval
2015-09-11 3:58 ` Qu Wenruo
2015-09-11 4:15 ` Omar Sandoval
2015-09-22 14:41 ` David Sterba
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=20150901193715.GA24255@huxley.DHCP.TheFacebook.com \
--to=osandov@osandov.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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;
as well as URLs for NNTP newsgroup(s).