From: Victor Yodaiken <yodaiken@fsmlabs.com>
To: BALBIR SINGH <balbir.singh@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] I still see people using cli()
Date: Mon, 8 Oct 2001 08:49:50 -0600 [thread overview]
Message-ID: <20011008084950.B16204@hq2> (raw)
In-Reply-To: <3BC1B831.1060601@wipro.com>
On Mon, Oct 08, 2001 at 07:59:05PM +0530, BALBIR SINGH wrote:
> BTW, that brings me to another issue, once the kernel becomes preemptibel, what
> are the locking issues? how are semaphores and spin-locks affected? Has anybody
> defined or come up with the rules/document yet?
IF the kernel becomes preemptible it will be so slow, so buggy, and so painful
to maintain, that those issues won't matter.
next prev parent reply other threads:[~2001-10-08 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 14:29 [RFC] I still see people using cli() BALBIR SINGH
2001-10-08 14:49 ` Victor Yodaiken [this message]
2001-10-08 15:11 ` Eric W. Biederman
2001-10-08 15:42 ` Victor Yodaiken
2001-10-08 16:45 ` Eric W. Biederman
2001-10-08 17:12 ` Victor Yodaiken
2001-10-08 19:09 ` Eric W. Biederman
2001-10-08 19:42 ` Victor Yodaiken
2001-10-08 18:11 ` george anzinger
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=20011008084950.B16204@hq2 \
--to=yodaiken@fsmlabs.com \
--cc=balbir.singh@wipro.com \
--cc=linux-kernel@vger.kernel.org \
/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