From: Daniel Walker <dwalker@codeaurora.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH v0] add nano semaphore in kernel
Date: Wed, 29 Dec 2010 06:58:07 -0800 [thread overview]
Message-ID: <1293634687.4128.10.camel@m0nster> (raw)
In-Reply-To: <AANLkTikGe3D-ujM9jqcOtk1cGmtLtUiV3kMkam1N8fyM@mail.gmail.com>
On Wed, 2010-12-29 at 22:42 +0800, Hillf Danton wrote:
> On Wed, Dec 29, 2010 at 7:47 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 28 December 2010 16:51:30 Daniel Walker wrote:
> >> We for sure don't want new semaphores, or new semaphore usage in the
> >> kernel ..
>
> Would you please, Daniel, explain why there are so my file systems under
> the fs directory? Would you think the ext file system is better than others?
>
> And why there are in kernel spin lock, read/write lock, mutex, rw_mutex,
> rtmutx, and semaphore, timer and hrtimer?
>
> Could timer be removed tonight?
The problem with semaphores is that people use them in ways that are not
very nice, and not very efficient.. Since they are so flexible they can
be used in all sorts of ways, many of which are not clean. This is why,
if you read the kernel history, most semaphore have been removed from
the kernel and replaced with much nicer and cleaner mutexes.
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.
next prev parent reply other threads:[~2010-12-29 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 5:13 Hillf Danton
2010-12-26 6:46 ` Rakib Mullick
2010-12-26 7:04 ` Hillf Danton
2010-12-26 9:08 ` Rakib Mullick
2010-12-26 12:05 ` Hillf Danton
2010-12-26 12:56 ` Rakib Mullick
2010-12-27 14:04 ` Hillf Danton
2010-12-27 20:08 ` Randy Dunlap
2010-12-29 14:57 ` Hillf Danton
2010-12-27 21:15 ` Arnd Bergmann
2010-12-28 13:13 ` Hillf Danton
2010-12-28 15:51 ` Daniel Walker
2010-12-29 11:47 ` Arnd Bergmann
2010-12-29 14:42 ` Hillf Danton
2010-12-29 14:58 ` Daniel Walker [this message]
2010-12-29 15:03 ` Hillf Danton
2010-12-29 19:16 ` Arnd Bergmann
2010-12-30 14:21 ` Hillf Danton
2010-12-30 15:56 ` Arnd Bergmann
2011-01-04 14:03 ` Pavel Machek
2011-01-04 14:18 ` Hillf Danton
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=1293634687.4128.10.camel@m0nster \
--to=dwalker@codeaurora.org \
--cc=arnd@arndb.de \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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
Powered by JetHome