Linux NILFS development
 help / color / mirror / Atom feed
From: Pierre Etchemaite <petchema-5XhUwtNo+r9Wk0Htik3J/w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Unknown symbol __umoddi3 / ... __udivdi3
Date: Wed, 12 Dec 2007 11:45:14 +0100	[thread overview]
Message-ID: <475FBBBA.10602@agematis.com> (raw)

    Hello all,

First, I believe log based filesystems are the future; Not only for 
snapshot feature, but also because they can give superior performance 
(vs. standard filesystems) on modern disks, cf

http://citeseer.ist.psu.edu/694627.html

for a very interesting performance analysis.


Now, back to more down-to-earth considerations :)
I'd like to give the nilfs 2.0.0-testing7 release a try with linux 
kernel 2.6.23, but I can't load the kernel module; dmesg says

nilfs2: Unknown symbol __umoddi3
nilfs2: Unknown symbol __udivdi3
nilfs2: Unknown symbol __umoddi3
nilfs2: Unknown symbol __udivdi3
nilfs2: Unknown symbol __umoddi3
nilfs2: Unknown symbol __udivdi3

CPU is an AMD64 but used in 32 bit mode, and it seems that 64 bit 
divisions are a problem for 32 bit kernels :/
Any idea how to get around that? (using asm/div64.h?)

Best regards,
Pierre.

             reply	other threads:[~2007-12-12 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 10:45 Pierre Etchemaite [this message]
     [not found] ` <475FBBBA.10602-5XhUwtNo+r9Wk0Htik3J/w@public.gmane.org>
2008-01-04 11:46   ` Unknown symbol __umoddi3 / ... __udivdi3 amagai-sG5X7nlA6pw
     [not found]     ` <20080104114633.A71A53E06C1-121w62HK5dnR7s880joybQ@public.gmane.org>
2008-01-04 11:57       ` Pierre Etchemaite

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=475FBBBA.10602@agematis.com \
    --to=petchema-5xhuwtno+r9wk0htik3j/w@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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