All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Chris Friesen <cfriesen@nortel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: question on symbol exports
Date: Mon, 7 Feb 2005 18:42:24 -0500	[thread overview]
Message-ID: <bc4f2e60770528d4934b5a2e69285002@embeddededge.com> (raw)
In-Reply-To: <1107812101.7734.42.camel@gaston>


On Feb 7, 2005, at 4:35 PM, Benjamin Herrenschmidt wrote:

> Interesting... more than no swap, you must also make sure you have no
> r/w mmap'ed file (which are technically equivalent to swap).

Yeah, I kinda had a similar thought.  Just because you aren't
swapping doesn't mean the VM subsystem isn't looking at dirty bits,
too.  It could potentially steal a page that it thinks can be replaced
from either a zero-fill or reading again from persistent storage.


	-- Dan

WARNING: multiple messages have this Message-ID (diff)
From: Dan Malek <dan@embeddededge.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Arjan van de Ven <arjan@infradead.org>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Chris Friesen <cfriesen@nortel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: question on symbol exports
Date: Mon, 7 Feb 2005 18:42:24 -0500	[thread overview]
Message-ID: <bc4f2e60770528d4934b5a2e69285002@embeddededge.com> (raw)
In-Reply-To: <1107812101.7734.42.camel@gaston>


On Feb 7, 2005, at 4:35 PM, Benjamin Herrenschmidt wrote:

> Interesting... more than no swap, you must also make sure you have no
> r/w mmap'ed file (which are technically equivalent to swap).

Yeah, I kinda had a similar thought.  Just because you aren't
swapping doesn't mean the VM subsystem isn't looking at dirty bits,
too.  It could potentially steal a page that it thinks can be replaced
from either a zero-fill or reading again from persistent storage.


	-- Dan


  parent reply	other threads:[~2005-02-07 23:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  0:15 question on symbol exports Chris Friesen
2005-02-01  7:36 ` Arjan van de Ven
2005-02-01 15:37   ` Chris Friesen
2005-02-01 15:50     ` Arjan van de Ven
2005-02-01 17:00       ` Chris Friesen
     [not found]       ` <20050204203050.GA5889@dmt.cnet>
2005-02-04 20:14         ` Chris Friesen
2005-02-04 20:14           ` Chris Friesen
2005-02-05  9:19           ` Benjamin Herrenschmidt
2005-02-05  9:19             ` Benjamin Herrenschmidt
2005-02-07 14:44             ` Chris Friesen
2005-02-07 14:44               ` Chris Friesen
2005-02-07 21:35               ` Benjamin Herrenschmidt
2005-02-07 21:35                 ` Benjamin Herrenschmidt
2005-02-07 23:02                 ` Chris Friesen
2005-02-07 23:02                   ` Chris Friesen
2005-02-07 23:42                 ` Dan Malek [this message]
2005-02-07 23:42                   ` Dan Malek
2005-02-08 15:36                   ` Chris Friesen
2005-02-08 15:36                     ` Chris Friesen

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=bc4f2e60770528d4934b5a2e69285002@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=arjan@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.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.