linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, linux-arch@vger.kernel.org,
	benh@kernel.crashing.org, rmk@arm.linux.org.uk
Subject: Re: Software prefetching considered harmful
Date: Fri, 20 May 2011 01:34:00 +0200	[thread overview]
Message-ID: <20110519233400.GA1954@elte.hu> (raw)
In-Reply-To: <20110519.154700.1253349185128359804.davem@davemloft.net>


* David Miller <davem@davemloft.net> wrote:

> So, to reiterate, I think you should kill all the list handling
> prefetches off.

Agreed.

> What we can do is say "for this specific list use, prefetch does
> in fact help".  And provide an interface for that.  I imagine there
> are things like inode dirty writeback or some dcache stuff that
> walks large lists and for which prefetch might be appropriate.

I think the best 'interface' for that is to open-code the prefetch()
right into the loop. This way it becomes well documented and very
visible as well.

Thanks,

	Ingo

  reply	other threads:[~2011-05-19 23:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 17:12 Software prefetching considered harmful Linus Torvalds
2011-05-19 19:05 ` Linus Torvalds
2011-05-19 19:28   ` Ingo Molnar
2011-05-21  3:37     ` Michael Cree
2011-05-21  4:18       ` Benjamin Herrenschmidt
2011-05-21 10:42         ` Ingo Molnar
2011-05-19 19:32   ` David Miller
2011-05-19 19:38     ` Linus Torvalds
2011-05-19 19:47       ` David Miller
2011-05-19 23:34         ` Ingo Molnar [this message]
2011-05-20 16:01           ` Catalin Marinas
2011-05-20  1:42   ` Benjamin Herrenschmidt
2011-05-20  8:34     ` Ingo Molnar
2011-05-20  9:13       ` Benjamin Herrenschmidt

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=20110519233400.GA1954@elte.hu \
    --to=mingo@elte.hu \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).