From: Pierre Ossman <drzeus@drzeus.cx>
To: Neil Horman <nhorman@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>, Pekka Paalanen <pq@iki.fi>
Subject: Re: [PATCH 0/4] [GIT PULL] memory saving ring buffer for tip/tracing/ftrace
Date: Thu, 12 Mar 2009 13:12:07 +0100 [thread overview]
Message-ID: <20090312131207.1c7fa213@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090312104721.GA6005@shamino.rdu.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Thu, 12 Mar 2009 06:47:21 -0400
Neil Horman <nhorman@redhat.com> wrote:
> On Thu, Mar 12, 2009 at 08:07:58AM +0100, Pierre Ossman wrote:
> >
> > How difficult is it to apply this to 2.6.27? Fedora is still on that
> > kernel and it would be nice if I could get my memory back on a
> > distribution kernel. :)
>
> I'm looking into it currently. I'll post a test kernel when I have something
> for you.
F9 kernel if possible, as that's what the test machine is running.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-03-12 12:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 2:37 Steven Rostedt
2009-03-12 2:37 ` [PATCH 1/4] tracing: keep ring buffer to minimum size till used Steven Rostedt
2009-03-12 3:26 ` Andrew Morton
2009-03-12 13:25 ` Steven Rostedt
2009-03-12 15:01 ` Frederic Weisbecker
2009-03-12 15:14 ` Steven Rostedt
2009-03-12 2:37 ` [PATCH 2/4] tracing: expand the ring buffers when an event is activated Steven Rostedt
2009-03-12 2:37 ` [PATCH 3/4] tracing: fix trace_wait to know to wait on all cpus or just one Steven Rostedt
2009-03-12 2:37 ` [PATCH 4/4] ring-buffer: only allocate buffers for online cpus Steven Rostedt
2009-03-12 3:32 ` Andrew Morton
2009-03-12 13:29 ` Steven Rostedt
2009-03-12 7:31 ` KOSAKI Motohiro
2009-03-12 13:38 ` Steven Rostedt
2009-03-12 23:47 ` KOSAKI Motohiro
2009-03-12 7:07 ` [PATCH 0/4] [GIT PULL] memory saving ring buffer for tip/tracing/ftrace Pierre Ossman
2009-03-12 7:34 ` KOSAKI Motohiro
2009-03-12 9:20 ` Pierre Ossman
2009-03-12 13:39 ` Steven Rostedt
2009-03-12 10:47 ` Neil Horman
2009-03-12 12:12 ` Pierre Ossman [this message]
2009-03-12 13:12 ` Neil Horman
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=20090312131207.1c7fa213@mjolnir.ossman.eu \
--to=drzeus@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@redhat.com \
--cc=peterz@infradead.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®