public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] break_lock forever broken
Date: Mon, 14 Mar 2005 22:01:45 +1100	[thread overview]
Message-ID: <42356F19.7060307@yahoo.com.au> (raw)
In-Reply-To: <20050314104611.GA30392@elte.hu>

Ingo Molnar wrote:
> * Arjan van de Ven <arjan@infradead.org> wrote:
> 
> 
>>as I said, since the cacheline just got dirtied, the write is just
>>half a cycle which is so much in the noise that it really doesn't
>>matter.
> 
> 
> ok - the patch below is a small modification of Hugh's so that we clear
> ->break_lock unconditionally. Since this code is not inlined it ought to
> have minimal icache impact too.
> 

Fine by me.


      reply	other threads:[~2005-03-14 11:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 18:51 [PATCH] break_lock forever broken Hugh Dickins
2005-03-12  4:34 ` Andrew Morton
2005-03-12 23:20   ` Hugh Dickins
2005-03-13  8:23     ` Arjan van de Ven
2005-03-13  9:35       ` Hugh Dickins
2005-03-13 13:52         ` Arjan van de Ven
2005-03-14  5:01     ` Nick Piggin
2005-03-14  7:02     ` Ingo Molnar
2005-03-14  8:03       ` Nick Piggin
2005-03-14  8:14         ` Ingo Molnar
2005-03-14  8:24           ` Nick Piggin
2005-03-14  8:34             ` Arjan van de Ven
2005-03-14  8:43               ` Nick Piggin
2005-03-14 10:46               ` Ingo Molnar
2005-03-14 11:01                 ` Nick Piggin [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=42356F19.7060307@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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