From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <peter@chubb.wattle.id.au>
Cc: <sct@redhat.com>, <raid@a2000.nu>, <adilger@clusterfs.com>,
<linux-kernel@vger.kernel.org>, <linux-raid@vger.kernel.org>,
<ext2-devel@lists.sourceforge.net>, <tytso@mit.edu>,
<tbm@a2000.nu>
Subject: Re: [Ext2-devel] Re: fsck out of memory
Date: Wed, 12 Feb 2003 20:01:57 -0800 (PST) [thread overview]
Message-ID: <32910.4.64.238.61.1045108917.squirrel@www.osdl.org> (raw)
In-Reply-To: <15947.4435.829168.530565@wombat.chubb.wattle.id.au>
>>>>>> "Stephen" == Stephen C Tweedie <sct@redhat.com> writes:
>
> Stephen> Hi, On Tue, 2003-02-11 at 13:11, Stephan van Hienen wrote:
>
> Stephen> I've no idea. Ben has some lb patches up at
>
> Stephen> http://people.redhat.com/bcrl/lb/
>
> Stephen> but there's nothing broken out against the latest lbd diffs.
>
>
> Ben's patches are against a very old version of the kernel (2.4.6-pre8) and
> require linking against libgcc to get 64-bit division.
>
>
> The main issue is 64-bit division. In the limited time I had I
> couldn't convince myself that I could rely on all divisors being less than
> 2^31 in the raid4/5 code. If you can convince yourself of that, then t's a
> straightforward but tedious task to make raid1, raid4 and raid5 LBD-safe.
> --
Hi,
Is this in a speed-sensitive area?
If not, you could consider 64-bit software divide functions, such as found at
http://nemesis.sourceforge.net/browse/lib/static/intmath/ix86/intmath.c.html,
which would only be used on 32-bit CPUs, of course.
--
~Randy
next prev parent reply other threads:[~2003-02-13 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5250726@toto.iv>
2003-02-13 3:30 ` Peter Chubb
2003-02-13 4:01 ` Randy.Dunlap [this message]
2003-02-07 15:17 kernel
2003-02-07 17:07 ` Stephan van Hienen
2003-02-07 17:28 ` Andreas Dilger
2003-02-09 10:08 ` Stephan van Hienen
2003-02-10 22:44 ` [Ext2-devel] " Stephen C. Tweedie
2003-02-11 13:11 ` Stephan van Hienen
2003-02-11 14:33 ` Stephen C. Tweedie
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=32910.4.64.238.61.1045108917.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=adilger@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=raid@a2000.nu \
--cc=sct@redhat.com \
--cc=tbm@a2000.nu \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®