public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: MM VM patches was: 2.6.3-mm4
Date: Mon, 01 Mar 2004 01:47:42 -0800	[thread overview]
Message-ID: <404306BE.6000803@matchmail.com> (raw)
In-Reply-To: <40430204.6040901@cyberone.com.au>

Nick Piggin wrote:
> 
> 
> Mike Fedyk wrote:
>> So, I'll merge up 2.6.3 + "vm of rc1-mm1" and tell you guys what I see.
>>
> 
> I'm not so hopeful for you anymore :P

These patches apply with only a few offsets if you apply them like in 
the series file, so there's not much work for either of us in applying 
these patches (unless I need to test without a dependent patch or 
something obvious like that...)

> 
>> Are the graphs helpful at all?
>>
> 
> 
> My eyes! The goggles, they do nothing!
> 

Heh.

> They have a lot of good info but I'm a bit hard pressed working
> out what kernel is running where

Suffice it to say, 2.6.3 is the begining of week9, and 2.6.3-lofft-mm4vm 
is the end of week9.  The graphs weren't meant to keep secondary 
information like kernel version...

> and it's a bit hard working out
> all the shades of blue on my crappy little monitor.

Yeah, I see what you mean.  The code in the lrrd/munin project controls 
what colors come in what order, but I can control what order the info is 
output in...

> But if they were easier to read I reckon they'd be useful ;)

I'd like for that to be true especially since I rewrote the memory 
plugin for munin to graph as much as was exported to userspace from the 
Linux kernel...

Did I miss anything? ;)

  reply	other threads:[~2004-03-01  9:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26  2:55 2.6.3-mm4 Andrew Morton
2004-02-26  8:22 ` 2.6.3-mm4 Alexander Hoogerhuis
2004-02-26  8:48   ` 2.6.3-mm4 Marc-Christian Petersen
2004-02-26  8:51 ` 2.6.3-mm4 Nuno Silva
2004-02-27  0:48   ` 2.6.3-mm4 Greg KH
2004-02-26 15:50 ` 2.6.3-mm4 David Martínez Moreno
2004-02-26 15:59   ` 2.6.3-mm4 Christoph Hellwig
2004-02-26 16:30 ` 2.6.3-mm4 (compile stats) John Cherry
2004-02-26 18:59   ` Mike Fedyk
2004-02-26 19:26     ` John Cherry
2004-02-26 18:50 ` 2.6.3-mm4 Matthias Hentges
2004-02-26 23:35 ` 2.6.3-mm4, sensors broken Prakash K. Cheemplavam
2004-02-27  0:03   ` Andrew Morton
2004-02-27  8:58     ` Prakash K. Cheemplavam
2004-02-27  0:11 ` 2.6.3-mm4 J.A. Magallon
2004-02-27  0:46   ` 2.6.3-mm4 Greg KH
2004-02-27  8:35     ` 2.6.3-mm4 Jean Delvare
2004-02-27 18:16       ` 2.6.3-mm4 Mike Fedyk
2004-02-27 19:59         ` 2.6.3-mm4 Jean Delvare
2004-02-29  7:51           ` 2.6.3-mm4 Mike Fedyk
2004-02-29 10:11             ` 2.6.3-mm4 Jean Delvare
2004-02-27 16:48     ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27  9:00   ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27 23:51 ` 2.6.3-mm4 Adrian Bunk
2004-03-01  8:25 ` MM VM patches was: 2.6.3-mm4 Mike Fedyk
2004-03-01  8:44   ` Nick Piggin
2004-03-01  9:05     ` Mike Fedyk
2004-03-01  9:27       ` Nick Piggin
2004-03-01  9:47         ` Mike Fedyk [this message]
2004-03-01  9:10     ` Nick Piggin
2004-03-01  9:52       ` [PATCH] 2.6.4-rc1-mm1: vm-kswapd-incremental-min (was Re: MM VM patches was: 2.6.3-mm4) Nick Piggin
2004-03-01 10:18         ` Andrew Morton
2004-03-01 10:29           ` Nick Piggin

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=404306BE.6000803@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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