[lkml]   [2018]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/2] bcachefs: On disk data structures
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.


 \ /
  Last update: 2018-05-14 00:50    [W:0.058 / U:4.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site