From: Vladimir Saveliev <vs@namesys.com>
To: "Markus TЖrnqvist" <mjt@nysv.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Where Reiser4 may break?
Date: Thu, 27 May 2004 13:00:05 +0400 [thread overview]
Message-ID: <1085648404.1915.219.camel@tribesman.namesys.com> (raw)
In-Reply-To: <20040526204457.GJ4990@nysv.org>
Hello
On Thu, 2004-05-27 at 00:44, Markus TÆrnqvist wrote:
> Hi
>
> I was thinking about some potential problems.
>
> Actually, Nikita and I had a discussion about the issues with
> cross-architecture compatibility. It would apparently not be easy to
> do, because block size equals page size in Reiser4.
>
yes, now moving a hard drive with reiser4 between systems with different
page size is impossible.
> Is this common with other file systems?
no
> I didn't get to ask that
> question so to get an answer :)
>
> Just when stuff like FireWire and USB hard drives are getting popular
> and no-one should buy a PC laptop, this may become an issue for
> PPC Linux users...
>
> Then, the issues with small and large keys. Is there any need for two
> sizes? Isn't it hazardous that some peoples' systems may cease to
> function because of that? It seems larger keys are far superior...
>
Both large and small keys should be supported such that user does not
have to care of compile option
It was made compile option because there was a desire to try it as fast
as possible.
> Any performance issues, anything?
>
> Thanks!
next prev parent reply other threads:[~2004-05-27 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 20:44 Where Reiser4 may break? mjt
2004-05-27 9:00 ` Vladimir Saveliev [this message]
2004-05-27 9:25 ` mjt
2004-05-27 10:44 ` Vladimir Saveliev
2004-05-27 21:30 ` David Masover
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=1085648404.1915.219.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.