mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "liang yuanen" <linux.kernel.liang@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why are we reduce spin-lock and replace it with lock-free?
Date: Thu, 10 May 2007 15:32:41 +0100	[thread overview]
Message-ID: <20070510153241.2d5ac2cb@the-village.bc.nu> (raw)
In-Reply-To: <76391b770705100723w24c93b99m48180a759d2116c7@mail.gmail.com>

On Thu, 10 May 2007 22:23:32 +0800
"liang yuanen" <linux.kernel.liang@gmail.com> wrote:

> Three are many many spin-lock in the kernel code, and in multi-core
> conditions, it push down the kernel performance.why are we reduce
> spin-lock and replace it with lock-free?

If you can find algorithms which are lock free, faster than taking the
lock and have bounded resource consumption then you can test them with
the kernel and send patches. 

Alan

      reply	other threads:[~2007-05-10 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 14:23 liang yuanen
2007-05-10 14:32 ` Alan Cox [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=20070510153241.2d5ac2cb@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.kernel.liang@gmail.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

all inboxes | Powered by JetHome®