From: Corey Minyard <minyard@acm.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] fs/ocfs2/alloc.c too big
Date: Thu, 24 Apr 2008 15:37:26 -0000 [thread overview]
Message-ID: <4810A918.4080705@acm.org> (raw)
When compiling fs/ocfs2/alloc.c for a MIPS platform, the size of the
section became too large for the jump using in MIPS atomics to reach the
places it needs to go. I've split up alloc.c into three files (tree.c
and truncate.c) to fix it for now where I'm working.
I'm curious if this has already been done. It could be argued that the
MIPS code needs to be fixed to handle the size, but that would slow down
the atomics and I think >6000 lines is probably too big, anyway. I'm
willing to split it up in the current code base, if the maintainers are
willing to accept the change.
Thanks,
-corey
reply other threads:[~2008-04-24 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4810A918.4080705@acm.org \
--to=minyard@acm.org \
--cc=ocfs2-devel@oss.oracle.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.