All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Patch to fix lfetches accessing beyond a page (c
Date: Wed, 17 Apr 2002 21:42:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905478@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905475@msgid-missing>

>>>>> On Wed, 17 Apr 2002 13:35:13 -0700, "Mallick, Asit K" <asit.k.mallick@intel.com> said:

  Asit> But I also think that the code should not access memory beyond
  Asit> the page even though it does not affect the functionality as
  Asit> these are hints. These accesses can also cause performance
  Asit> problems.

Ah, now *that's* an argument I can live with. ;-)

I just don't want there to be any confusion about whether or not
lfetch to arbitrary addresses is legal.  It must be, as hardware is
allowed to prefetch on its own.

	--david


      parent reply	other threads:[~2002-04-17 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 18:51 [Linux-ia64] Patch to fix lfetches accessing beyond a page (copy_page/clear_pa Mallick, Asit K
2002-04-17 19:35 ` David Mosberger
2002-04-17 20:35 ` [Linux-ia64] Patch to fix lfetches accessing beyond a page (c Mallick, Asit K
2002-04-17 21:42 ` David Mosberger [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=marc-linux-ia64-105590701905478@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.