From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Adrian Bunk <bunk@kernel.org>,
sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
zippel@linux-m68k.org, linux-ext4@vger.kernel.org,
linux-m68k@vger.kernel.org
Subject: Re: ext4 compile error on m68k
Date: Thu, 10 Apr 2008 19:28:07 +0530 [thread overview]
Message-ID: <20080410135807.GA7526@skywalker> (raw)
In-Reply-To: <je7if69bh4.fsf@sykes.suse.de>
On Thu, Apr 10, 2008 at 01:48:55PM +0200, Andreas Schwab wrote:
> "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
>
> > But m68k doesn't want to use the GENERIC_FIND_NEXT_BIT. Can I request
> > somebody knowledgeable about m68k to give a try in implementing
> > generic_find_next_le_bit equivalent on m68k ?
>
> What's the exact semantic of generic_find_next_le_bit? Why is it not
> documented?
>
Should be same ext2_find_next_zero_bit except that it find the next
set bit rather than the zero bit. The API is used to find the set bit
in bitmap. To explain the little endian dependency, what we have is
0 x n
[.......1.......]
Now we read this as (char *) and try to find the first set bit which
in the above example is x. To speed up most of the architectures would
like to consider it as an array of long. That implies that the value
in the array should be considered as a little endian long, hence the
*_le_bit.
-aneesh
next prev parent reply other threads:[~2008-04-10 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 10:24 ext4 compile error on m68k Adrian Bunk
2008-04-05 11:48 ` Geert Uytterhoeven
2008-04-10 10:41 ` Aneesh Kumar K.V
2008-04-10 11:26 ` Aneesh Kumar K.V
2008-04-10 11:48 ` Andreas Schwab
2008-04-10 13:58 ` Aneesh Kumar K.V [this message]
2008-04-10 14:01 ` Christoph Hellwig
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=20080410135807.GA7526@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@suse.de \
--cc=sct@redhat.com \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).