From: "David S. Miller" <davem@redhat.com>
To: akpm@zip.com.au
Cc: mingo@elte.hu, velco@fadata.bg, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH] Scalable page cache
Date: Mon, 26 Nov 2001 11:57:23 -0800 (PST) [thread overview]
Message-ID: <20011126.115723.41632923.davem@redhat.com> (raw)
In-Reply-To: <3C029BE0.2BEA2264@zip.com.au>
In-Reply-To: <Pine.LNX.4.33.0111262201420.18923-100000@localhost.localdomain> <20011126.111854.102567147.davem@redhat.com> <3C029BE0.2BEA2264@zip.com.au>
From: Andrew Morton <akpm@zip.com.au>
Date: Mon, 26 Nov 2001 11:45:36 -0800
It would be nice to have a full complement of non-atomic
bitops. At present we have __set_bit, but no __clear_bit, etc.
So we often do buslocked RMW's in places where it's not needed.
I totally agree about fixing up bitops.
I have a patch which cleans up the filesystem bitops. Specifically,
right now we use things like "ext2_set_bit()" in places where we care
what the old value was and also in places where we don't.
So I added "ext2_test_and_set_bit()" and the like.
I therefore plan to flesh this out, and flesh out the non-atomic
bitops, then resubmit.
I did the work originally during 2.4.15-preX which made me have to
back it out of my tree temporarily while Linus was in anal patch
acceptance mode.
Ahh, speaking of bitops, what's the status of the ext3 bitops bugs I
found Andrew? :-) Those are pretty serious.
next prev parent reply other threads:[~2001-11-26 19:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 12:31 [PATCH] Scalable page cache Momchil Velikov
2001-11-26 17:22 ` Ingo Molnar
2001-11-26 17:23 ` Momchil Velikov
2001-11-26 18:16 ` Benjamin LaHaise
2001-11-26 18:42 ` Rik van Riel
2001-11-26 20:29 ` Ingo Molnar
2001-11-26 18:33 ` David S. Miller
2001-11-26 19:29 ` Andrew Morton
2001-11-26 19:35 ` David S. Miller
2001-11-26 18:34 ` Benjamin LaHaise
2001-11-26 20:40 ` Ingo Molnar
2001-11-26 19:19 ` Benjamin LaHaise
2001-11-26 21:00 ` Ingo Molnar
2001-11-26 20:43 ` Daniel Phillips
2001-11-26 19:49 ` Ingo Molnar
2001-11-26 18:08 ` Christoph Hellwig
2001-11-26 20:13 ` Ingo Molnar
2001-11-26 21:09 ` Ingo Molnar
2001-11-26 19:18 ` David S. Miller
2001-11-26 19:45 ` Andrew Morton
2001-11-26 19:57 ` David S. Miller [this message]
2001-11-26 20:03 ` Andrew Morton
2001-11-26 20:37 ` Linus Torvalds
2001-11-26 21:02 ` Andrew Morton
2001-11-26 22:23 ` Linus Torvalds
2001-11-26 22:49 ` Jeff Garzik
2001-11-26 23:06 ` Linus Torvalds
2001-11-26 21:10 ` Ingo Molnar
2001-11-26 17:29 ` Linus Torvalds
2001-11-26 20:03 ` Ingo Molnar
2001-11-26 18:02 ` David S. Miller
2001-11-26 18:11 ` Rik van Riel
2001-11-27 8:07 ` benchmark results: " Anton Blanchard
2001-11-26 18:52 ` [PATCH] " Daniel Phillips
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=20011126.115723.41632923.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
--cc=velco@fadata.bg \
/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.