mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: prasanna@in.ibm.com
Cc: Arjan van de Ven <arjan@infradead.org>,
	Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
	davem@davemloft.net, suparna@in.ibm.com,
	richardj_moore@uk.ibm.com, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: RFC - Approaches to user-space probes
Date: 28 Mar 2006 15:35:43 -0500	[thread overview]
Message-ID: <y0m64lye28w.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20060328145441.GA25465@in.ibm.com>

Prasanna S Panchamukhi <prasanna@in.ibm.com> writes:

> [...]
> If the executable is mmaped shared, then those mappings will get written
> back to the disk.
> Writting to the disk is not the requirement for user-space probes, it is
> just the side effect [...]

It's pretty clear that writing the dirtied pages to disk is an
*undesirable* side-effect, and should be eliminated.  (Among many
other scenarios, imagine a kernel shutting down without all the probes
being cleanly removed.  Then the executables are irretrievably
corrupted.)

- FChE

  parent reply	other threads:[~2006-03-28 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27  6:54 Prasanna S Panchamukhi
2006-03-27  7:37 ` Arjan van de Ven
2006-03-27 10:00   ` Prasanna S Panchamukhi
2006-03-27 20:03     ` Arjan van de Ven
2006-03-28  9:42       ` Richard J Moore
2006-03-28  9:47         ` Andi Kleen
2006-03-28 10:10           ` Richard J Moore
2006-03-28 14:54       ` Prasanna S Panchamukhi
2006-03-28 17:29         ` Arjan van de Ven
2006-03-28 20:35         ` Frank Ch. Eigler [this message]
2006-03-28 20:44           ` Andi Kleen
2006-03-31 11:55           ` Prasanna S Panchamukhi
2006-03-31 16:25             ` Frank Ch. Eigler

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=y0m64lye28w.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=prasanna@in.ibm.com \
    --cc=richardj_moore@uk.ibm.com \
    --cc=suparna@in.ibm.com \
    --cc=tytso@mit.edu \
    /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

Powered by JetHome