From: "Stephen C. Tweedie" <sct@redhat.com>
To: masp0008@stud.uni-sb.de
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
"David S. Miller" <davem@dm.cobaltmicro.com>
Subject: Re: kernel_lock() profiling results
Date: Wed, 26 May 1999 20:22:20 +0100 (BST) [thread overview]
Message-ID: <14156.18924.10333.781178@dukat.scot.redhat.com> (raw)
In-Reply-To: <374C3237.2D89878@colorfullife.com>
Hi,
On Wed, 26 May 1999 19:41:11 +0200, Manfred Spraul
<manfreds@colorfullife.com> said:
> 1) Andrea noticed that 'unlock_kernel()' only releases the kernel lock
> if the lock was obtained once.
Yes, but in all the places we are currently doing the copy_*_user, we
only hold the lock once. In general we might want to do a true
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.
--Stephen
--
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-05-26 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 14:30 kernel_lock() profiling results 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 [this message]
1999-05-29 0:45 ` 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=14156.18924.10333.781178@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=davem@dm.cobaltmicro.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=masp0008@stud.uni-sb.de \
/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.