linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: torvalds@osdl.org, linux-kernel@vger.kernel.org, ak@suse.de
Cc: oprofile-list@lists.sourceforge.net
Subject: Re: [PATCH] OProfile: dynamically allocate MSR struct
Date: Mon, 14 Jul 2003 16:54:45 +0100	[thread overview]
Message-ID: <20030714155445.GA72180@compsoc.man.ac.uk> (raw)
In-Reply-To: <20030714151727.GA69617@compsoc.man.ac.uk>

On Mon, Jul 14, 2003 at 04:17:28PM +0100, John Levon wrote:

> Andi pointed out to me that cpu_msrs was a source of bloat. Dynamically
> allocate it instead. Tested on my SMP box.

Gah, bogus patch, please ignore.

thanks
john

      reply	other threads:[~2003-07-14 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 15:17 [PATCH] OProfile: dynamically allocate MSR struct John Levon
2003-07-14 15:54 ` John Levon [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=20030714155445.GA72180@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=torvalds@osdl.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).