From: Ingo Molnar <mingo@chiara.csoma.elte.hu>
To: Andrea Arcangeli <andrea@e-mind.com>
Cc: Mark Hemment <markhe@sco.COM>, Chuck Lever <cel@monkey.org>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [patch] only-one-cache-query [was Re: [patch] arca-vm-2.2.5]
Date: Wed, 7 Apr 1999 15:47:50 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.990407154601.30376E-100000@chiara.csoma.elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.05.9904070243310.222-100000@laser.random>
On Wed, 7 Apr 1999, Andrea Arcangeli wrote:
> void prune_dcache(int count)
> {
> + gfp_sleeping_cookie++;
this can be done via an existing variable, kstat.ctxsw, no need to add yet
another 'have we scheduled' flag. But the whole approach is quite flawed
and volatile, it simply relies on us having the big kernel lock. With more
finegrained SMP locking in that area we will have big problems preserving
that solution.
-- mingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-04-07 13:48 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 23:32 [patch] arca-vm-2.2.5 Andrea Arcangeli
1999-04-04 21:07 ` Chuck Lever
1999-04-05 0:22 ` Andrea Arcangeli
1999-04-05 13:23 ` Mark Hemment
1999-04-05 15:56 ` Andrea Arcangeli
1999-04-07 11:28 ` [patch] only-one-cache-query [was Re: [patch] arca-vm-2.2.5] Andrea Arcangeli
1999-04-07 13:06 ` Stephen C. Tweedie
1999-04-07 13:49 ` Andrea Arcangeli
1999-04-07 13:42 ` Andrea Arcangeli
1999-04-07 13:47 ` Ingo Molnar [this message]
1999-04-07 14:08 ` Andrea Arcangeli
1999-04-05 20:24 ` [patch] arca-vm-2.2.5 Horst von Brand
1999-04-05 23:25 ` Andrea Arcangeli
1999-04-05 23:37 ` Horst von Brand
1999-04-06 1:23 ` Andrea Arcangeli
1999-04-17 11:12 ` Andrea Arcangeli
1999-04-05 21:31 ` Chuck Lever
1999-04-06 0:15 ` Andrea Arcangeli
1999-04-06 2:14 ` Doug Ledford
1999-04-06 13:04 ` Andrea Arcangeli
1999-04-06 21:31 ` Stephen C. Tweedie
1999-04-06 22:27 ` Andrea Arcangeli
1999-04-07 12:27 ` Stephen C. Tweedie
1999-04-25 3:22 ` Chuck Lever
1999-04-06 5:52 ` Chuck Lever
1999-04-06 13:09 ` Andrea Arcangeli
1999-04-06 16:19 ` Eric W. Biederman
1999-04-06 20:26 ` Andrea Arcangeli
1999-04-07 5:00 ` Eric W. Biederman
1999-04-07 11:36 ` Andrea Arcangeli
1999-04-06 14:02 ` Stephen C. Tweedie
1999-04-06 15:38 ` Chuck Lever
1999-04-06 17:16 ` Andrea Arcangeli
1999-04-06 18:07 ` Andrea Arcangeli
1999-04-06 21:22 ` Stephen C. Tweedie
1999-04-06 22:19 ` Ingo Molnar
1999-04-06 22:40 ` David Miller
1999-04-06 22:49 ` Ingo Molnar
1999-04-06 22:53 ` David Miller
1999-04-07 15:59 ` Gabriel Paubert
1999-04-07 21:07 ` Arvind Sankar
1999-04-09 6:58 ` Eric W. Biederman
1999-04-09 9:27 ` Gabriel Paubert
1999-04-09 15:40 ` Eric W. Biederman
1999-04-08 8:09 ` Carlo Daffara
1999-04-06 22:31 ` Andrea Arcangeli
1999-04-06 20:47 ` Chuck Lever
1999-04-06 21:04 ` Andrea Arcangeli
1999-04-06 21:11 ` Stephen C. Tweedie
1999-04-06 14:00 ` Stephen C. Tweedie
1999-04-06 16:29 ` Andrea Arcangeli
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=Pine.LNX.3.96.990407154601.30376E-100000@chiara.csoma.elte.hu \
--to=mingo@chiara.csoma.elte.hu \
--cc=andrea@e-mind.com \
--cc=cel@monkey.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=markhe@sco.COM \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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