linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Nick Piggin <npiggin@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	shaggy@austin.ibm.com, axboe@kernel.dk, linux-mm@kvack.org,
	linux-arch@vger.kernel.org, Clark Williams <williams@redhat.com>,
	Ingo Molnar <mingo@elte.hu>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [patch 2/2]: introduce fast_gup
Date: Fri, 18 Apr 2008 07:40:14 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.00.0804180734530.2879@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0804180831000.9489@anakin>


On Fri, 18 Apr 2008, Geert Uytterhoeven wrote:
> On Thu, 17 Apr 2008, Peter Zijlstra wrote:
> > +retry:
> > +	pte.pte_low = ptep->pte_low;
> > +	smp_rmb();
> > +	pte.pte_high = ptep->pte_high;
> > +	smp_rmb();
> > +	if (unlikely(pte.pte_low != ptep->pte_low))
> > +		goto retry;
> 
> What about using `do { ... } while (...)' instead?

Partly because it's not a loop. It's an error and retry event, and it 
generally happens zero times (and sometimes once). I don't think it should 
even _look_ like a loop.

So personally, I just tend to think that it's just more readable when it's 
written as being obviously not a regular loop. I'm not in the "gotos are 
harmful" camp.

And partly because I tend to distrust loops for these thigns is that 
historically gcc sometimes did stupid things for loops (it assumed that 
loops were hot and tried to align them etc, and the same didn't happen for 
branch targets). Of course, these days I suspect gcc can't even tell the 
difference any more (it probably turns it into the same internal 
representation), but old habits die hard.

			Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-04-18 14:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  2:54 [patch 0/2]: lockless get_user_pages patchset Nick Piggin
2008-03-28  2:55 ` [patch 1/2]: x86: implement pte_special Nick Piggin
2008-03-28  3:23   ` David Miller, Nick Piggin
2008-03-28  3:31     ` Nick Piggin
2008-03-28  3:44       ` David Miller, Nick Piggin
2008-03-28  4:04         ` Nick Piggin
2008-03-28  4:09           ` David Miller, Nick Piggin
2008-03-28  4:15             ` Nick Piggin
2008-03-28  4:16               ` David Miller, Nick Piggin
2008-03-28  4:19                 ` Nick Piggin
2008-03-28  4:17               ` Nick Piggin
2008-03-28  3:00 ` [patch 2/2]: introduce fast_gup Nick Piggin
2008-03-28 10:01   ` Jens Axboe
2008-04-17 15:03   ` Peter Zijlstra
2008-04-17 15:25     ` Linus Torvalds
2008-04-17 16:12       ` Peter Zijlstra
2008-04-17 16:18         ` Linus Torvalds
2008-04-17 16:35           ` Peter Zijlstra
2008-04-17 16:40             ` Linus Torvalds
2008-04-17 17:23               ` Peter Zijlstra
2008-04-17 18:28                 ` Linus Torvalds
2008-04-22  3:14                   ` Nick Piggin
2008-04-18  6:31                 ` Geert Uytterhoeven
2008-04-18 14:40                   ` Linus Torvalds [this message]
2008-04-18  9:58         ` Jeremy Fitzhardinge
2008-04-21 12:00       ` Avi Kivity
2008-04-21 12:30         ` Peter Zijlstra
2008-04-21 13:26           ` Avi Kivity
2008-04-21 14:35             ` Peter Zijlstra
2008-04-22  3:23               ` Nick Piggin
2008-04-22  7:19                 ` Avi Kivity
2008-04-22  8:07                 ` Ingo Molnar
2008-04-22  9:42   ` Peter Zijlstra
2008-04-22  9:46     ` Nick Piggin
2008-05-14 18:33       ` Dave Kleikamp
2008-05-15  1:13         ` Nick Piggin

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=alpine.LFD.1.00.0804180734530.2879@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=geert@linux-m68k.org \
    --cc=jeremy@goop.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=peterz@infradead.org \
    --cc=shaggy@austin.ibm.com \
    --cc=williams@redhat.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