From: David Sterba <dsterba@suse.cz>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/7] Patches to support subpagesize blocksize
Date: Fri, 13 Dec 2013 16:58:50 +0100 [thread overview]
Message-ID: <20131213155850.GZ6498@suse.cz> (raw)
In-Reply-To: <1386947820.4241.22.camel@chandra-dt.ibm.com>
On Fri, Dec 13, 2013 at 09:17:00AM -0600, Chandra Seetharaman wrote:
> > For a full compatibility with any blocksize on arch with any pagesize
> > you'd need to implement the case when sectorsize is larger than
> > pagesize. Your patchset does the "4k sector/64k page", but I haven't
> > noticed the "64k sector/4k page" counterpart.
>
> My object was to make btrfs filesystems from other arches to be directly
> usable in PPC64.
Ok then.
> Nevertheless, IIUC, btrfs currently support such a case. Each extent
> buffers currently can have up to INLINE_EXTENT_BUFFER_PAGES(16).
>
> -------
> #define INLINE_EXTENT_BUFFER_PAGES 16
>
> struct extent_buffer {
> :
> :
> struct page *pages[INLINE_EXTENT_BUFFER_PAGES];
> :
> };
> --------
>
> No ?
Just for metadata blocks.
> There are some issues with relocation too. Is there similar assumption
> in that code path too ?
I don't know. If yes, then it's different from the compression issues,
because there are some hardwired assumptions about the binary format of
the compressed data, while relocation uses the common code.
next prev parent reply other threads:[~2013-12-13 15:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 23:38 [PATCH 0/7] Patches to support subpagesize blocksize Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 1/7] btrfs: subpagesize-blocksize: Define extent_buffer_head Chandra Seetharaman
2013-12-16 12:32 ` saeed bishara
2013-12-16 16:17 ` Chandra Seetharaman
2013-12-17 15:35 ` David Sterba
2013-12-11 23:38 ` [PATCH 2/7] btrfs: subpagesize-blocksize: Use a global alignment for size Chandra Seetharaman
2013-12-16 12:33 ` saeed bishara
2013-12-16 14:48 ` David Sterba
2013-12-16 16:18 ` Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 3/7] btrfs: subpagesize-blocksize: Handle small extent maps properly Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 4/7] btrfs: subpagesize-blocksize: Handle iosize properly in submit_extent_page() Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 5/7] btrfs: subpagesize-blocksize: handle checksum calculations properly Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 6/7] btrfs: subpagesize-blocksize: Handle relocation clusters appropriately Chandra Seetharaman
2013-12-11 23:38 ` [PATCH 7/7] btrfs: subpagesize-blocksize: Allow mounting filesystems where sectorsize != PAGE_SIZE Chandra Seetharaman
2013-12-13 1:07 ` David Sterba
2013-12-16 12:50 ` saeed bishara
2013-12-12 20:40 ` [PATCH 0/7] Patches to support subpagesize blocksize Josef Bacik
2013-12-13 1:17 ` David Sterba
2013-12-13 15:17 ` Chandra Seetharaman
2013-12-13 15:58 ` David Sterba [this message]
2013-12-13 18:39 ` Josef Bacik
2013-12-13 22:09 ` Chandra Seetharaman
2014-01-08 20:06 ` Chandra Seetharaman
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=20131213155850.GZ6498@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sekharan@us.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;
as well as URLs for NNTP newsgroup(s).