From: Andrea Arcangeli <andrea@suse.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: masp0008@stud.uni-sb.de, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org, "David S. Miller" <davem@dm.cobaltmicro.com>
Subject: Re: kernel_lock() profiling results
Date: Sat, 29 May 1999 02:45:20 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.05.9905290241440.1597-100000@laser.random> (raw)
In-Reply-To: <14156.18924.10333.781178@dukat.scot.redhat.com>
On Wed, 26 May 1999, Stephen C. Tweedie wrote:
>save/restore of lock_depth for a new, self-unlocking copy_*_user, but
>right now the droplock diffs still do the right thing the simple way.
I wouldn't call it the "right thing". It's also not simpler according to
me since to make sure that the unlock_kernel is really dropping the
kernel_flag spinlock you must check all entry paths and verify that
lock_depth is 0 at such time.
Andrea Arcangeli
--
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-29 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 14:30 Manfred Spraul
1999-05-26 16:34 ` Stephen C. Tweedie
1999-05-26 17:41 ` Manfred Spraul
1999-05-26 19:22 ` Stephen C. Tweedie
1999-05-29 0:45 ` Andrea Arcangeli [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=Pine.LNX.4.05.9905290241440.1597-100000@laser.random \
--to=andrea@suse.de \
--cc=davem@dm.cobaltmicro.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=masp0008@stud.uni-sb.de \
--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