From: Manfred Spraul <manfreds@colorfullife.com>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: "Eric W. Biederman" <ebiederm+eric@ccr.net>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [PATCHES]
Date: Mon, 24 May 1999 19:20:41 +0200 [thread overview]
Message-ID: <37498A69.FF40CFE3@colorfullife.com> (raw)
In-Reply-To: Pine.LNX.3.96.990523171206.21583A-100000@chiara.csoma.elte.hu
Ingo Molnar wrote:
> on my box the page cache is already completely parallel on SMP,
> we drop the kernel lock on entry into page-cache routines and
> re-lock it only if we call filesystem-specific code or
> buffer-cache code.
How have you called the 'release_kernel_lock()' function?
I found several lengthy operations in the kernel which
should also release the kernel lock.
(the slowest: clear_page() when called by get_free_page(GFP_WAIT))
--
Manfred
--
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/
prev parent reply other threads:[~1999-05-24 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 3:36 [PATCHES] Eric W. Biederman
1999-05-23 6:03 ` [PATCHES] Linus Torvalds
1999-05-23 14:54 ` [PATCHES] Eric W. Biederman
1999-05-23 15:49 ` [PATCHES] Ingo Molnar
1999-05-23 18:34 ` [PATCHES] Eric W. Biederman
1999-05-27 6:24 ` [PATCHES] Stephen C. Tweedie
1999-05-27 19:55 ` [PATCHES] Chuck Lever
1999-05-27 23:39 ` [PATCHES] Stephen C. Tweedie
1999-05-28 5:30 ` [PATCHES] Chuck Lever
1999-05-29 1:24 ` [PATCHES] Stephen C. Tweedie
1999-05-30 17:01 ` [PATCHES] Eric W. Biederman
1999-05-27 6:25 ` [PATCHES] Stephen C. Tweedie
1999-05-24 17:20 ` Manfred Spraul [this message]
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=37498A69.FF40CFE3@colorfullife.com \
--to=manfreds@colorfullife.com \
--cc=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=masp0008@stud.uni-sb.de \
--cc=mingo@chiara.csoma.elte.hu \
--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 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.