From: David Masover <ninja@slaphack.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: Vladimir Saveliev <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Where Reiser4 may break?
Date: Thu, 27 May 2004 16:30:10 -0500 [thread overview]
Message-ID: <40B65DE2.4060607@slaphack.com> (raw)
In-Reply-To: <20040527092541.GN4990@nysv.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Markus Törnqvist wrote:
[ ... ]
| Well, we'll see what the future brings in this.
| I couldn't care less about architecture-compatibility, but then again,
| I may start caring if the situation demands it :)
Do we gain any speed by not adding that compatibility? If so, it should
be optional (mkfs/mount option, not compile time). Maybe we should be
able to specify at mkfs time what architecture to optimize for (x86,
ppc, everything, etc.), but let it default to optimize for this one.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQLZd4ngHNmZLgCUhAQI+/w//eXFRJdpj9S3nGCv7dFB7MTNdkocib8Ys
JXph2dL0N7nO04WiVLkxFaAIYWmQVQ/pN9JTMX36PQVm8f/An5ltXJyb2516TZSy
rGxD+WR13uB26b6/c2CERT6yE93FHQAWFEgkJqtCsBYD2ICAIoa03qGdyWyefxQ5
Y3H7o340KIcOCzcNzDJvk66/VdZYG83KBaiMrg9fohPPV0d/gFbLSNguGJAHzh/B
TYAi5bucYPBCMRta5CpmccD721icDryrbHxibWxLdA7+ncJquCLb4zdBaeNLD3Qh
qoFxKxqvSZOwnXqCXKc2EgDT16a+bFOwj39xPynMeBXbuJrvVL0a70og7kGjMyf1
tRA4s7LflAMq0JldM/fRxbQb/RtCe2nxh5/p0V5wI2ZFWyilowYooZ3uWm4lqRWe
RPbCFxPeGuZqq782yhnln7iaPqrBK0PaaPqsBgousnacwQnfqaZl/D1QGqt03bUi
zR+hTvKbc1zv85f2LoprEA8HtdMXwzQH8AdK1E+0qW/bHI6EAGBtBXWE29QJDObe
mh0AZDstqcm9OiK75hEGPRPnjGs72S7TKwuX8eIk1kTxmiTQqvXsQmpGwWZOHRoD
z0qVFt0a3a9JQnMsC1UE6qpbxjK5oEzmj/l+MCiqQuobKm/oS6r1g0V0cVACCkg3
vE+bRcrGcDE=
=EIQc
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-05-27 21:30 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
2004-05-27 9:25 ` mjt
2004-05-27 10:44 ` Vladimir Saveliev
2004-05-27 21:30 ` David Masover [this message]
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=40B65DE2.4060607@slaphack.com \
--to=ninja@slaphack.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.