From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: sct@redhat.com, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] Re: [RFC] ext3/jbd race: releasing in-use journal_heads
Date: Tue, 8 Mar 2005 13:45:25 +0530 [thread overview]
Message-ID: <20050308081525.GA4085@in.ibm.com> (raw)
In-Reply-To: <20050307233742.79737606.akpm@osdl.org>
On Mon, Mar 07, 2005 at 11:37:42PM -0800, Andrew Morton wrote:
> Suparna Bhattacharya <suparna@in.ibm.com> wrote:
> >
> > (let me know if the interface in the patch
> > I just posted seems like the right direction to use when we go for the
> > cleanup)
>
> Well what are the semantics? Pass in an inclusive max_index and the gang
> lookup functions terminate when they hit an item whose index is greater
> than max_index? And return the number of items thus found?
Yes. (end_index or max_items, whichever it hits first)
>
> Seems sensible, and all the comparisons do the right thing if max_index = -1.
end_index is unsigned long - so -1 would imply highest index possible
... i.e. all items, subject to the radix_tree_maxindex (max_index used
internally in the radix tree code).
Regards
Suparna
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Ext2-devel mailing list
> Ext2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ext2-devel
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2005-03-08 8:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 19:54 [RFC] ext3/jbd race: releasing in-use journal_heads Stephen C. Tweedie
2005-03-04 23:17 ` [Ext2-devel] " Badari Pulavarty
2005-03-07 14:28 ` Stephen C. Tweedie
2005-03-05 0:04 ` Andrew Morton
2005-03-07 14:50 ` Jan Kara
2005-03-07 16:01 ` Stephen C. Tweedie
2005-03-07 16:40 ` Stephen C. Tweedie
2005-03-07 17:05 ` Stephen C. Tweedie
2005-03-07 20:31 ` Andrew Morton
2005-03-07 21:08 ` Stephen C. Tweedie
2005-03-07 21:11 ` Andrew Morton
2005-03-07 21:22 ` Stephen C. Tweedie
2005-03-07 23:13 ` Stephen C. Tweedie
2005-03-07 23:50 ` Andrew Morton
2005-03-08 6:28 ` [Ext2-devel] " Suparna Bhattacharya
2005-03-08 6:39 ` Suparna Bhattacharya
2005-03-08 6:46 ` Andrew Morton
2005-03-08 7:26 ` Suparna Bhattacharya
2005-03-08 7:37 ` Andrew Morton
2005-03-08 8:15 ` Suparna Bhattacharya [this message]
2005-03-08 9:28 ` Stephen C. Tweedie
2005-03-08 12:40 ` [PATCH] invalidate/o_direct livelock {was Re: [RFC] ext3/jbd race: releasing in-use journal_heads} Stephen C. Tweedie
2005-03-08 12:53 ` [RFC] ext3/jbd race: releasing in-use journal_heads Stephen C. Tweedie
2005-03-08 15:12 ` Jan Kara
2005-03-09 13:10 ` Stephen C. Tweedie
2005-03-09 13:28 ` Jan Kara
2005-03-09 15:12 ` 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=20050308081525.GA4085@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox