From: Randy Dunlap <rdunlap@infradead.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-bcache@vger.kernel.org, Dave Chinner <dchinner@redhat.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
hare@suse.com
Subject: Re: [PATCH 1/2] bcachefs: On disk data structures
Date: Sun, 13 May 2018 15:49:21 -0700 [thread overview]
Message-ID: <3bf4a87c-20fc-0b9f-1c27-c43d1c194b47@infradead.org> (raw)
In-Reply-To: <20180513222948.GA20114@kmo-pixel>
On 05/13/2018 03:29 PM, Kent Overstreet wrote:
> On Sun, May 13, 2018 at 01:30:06PM -0700, Randy Dunlap wrote:
>> On 05/08/2018 03:17 PM, Kent Overstreet wrote:
>
>>> + * various btrees. There are only a small number of btrees, they're not
>>> + * sharded - we have one btree for extents, another for inodes, et cetera.
>>
>> or shared?
>
> No, I mean sharded - we're e.g. not splitting up the extents btree into one
> btree per inode.
Got it, thanks.
>> I know that you have already answered a few comments about endianness,
>> so maybe you answered this and I missed it.
>>
>> Can a bcachefs fs be shared, a la NFS? I.e., can multiple different-endian
>> clients be accessing the same bcachefs?
>
> NFS works. I haven't tested NFS to different endian clients, wasn't aware there
> was any reason to... are there potential issues there I'm not aware of?
Not that I know of.
thanks,
--
~Randy
next prev parent reply other threads:[~2018-05-13 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 22:17 [PATCH 0/2] bcachefs: on disk data structures, ioctl interface - review requested for upstreaming Kent Overstreet
2018-05-08 22:17 ` [PATCH 1/2] bcachefs: On disk data structures Kent Overstreet
2018-05-11 8:32 ` Dave Chinner
2018-05-11 22:04 ` Kent Overstreet
2018-05-13 20:30 ` Randy Dunlap
2018-05-13 22:29 ` Kent Overstreet
2018-05-13 22:49 ` Randy Dunlap [this message]
2018-05-08 22:18 ` [PATCH 2/2] bcachefs: Ioctl interface Kent Overstreet
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=3bf4a87c-20fc-0b9f-1c27-c43d1c194b47@infradead.org \
--to=rdunlap@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=hare@suse.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).