linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm8
Date: Thu, 22 May 2003 23:18:15 -0700	[thread overview]
Message-ID: <17990000.1053670694@[10.10.2.4]> (raw)
In-Reply-To: <20030522021652.6601ed2b.akpm@digeo.com>

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm8/
> 
> . One anticipatory scheduler patch, but it's a big one.  I have not stress
>   tested it a lot.  If it explodes please report it and then boot with
>   elevator=deadline.
> 
> . The slab magazine layer code is in its hopefully-final state.
> 
> . Some VFS locking scalability work - stress testing of this would be
>   useful.

Well, unsure about the problems I reported earlier - seems to be related
to modem disconnects during SDET runs ... the hung session seems to lock
up the system somehow. But that could have been around for ages - I'll
try to be more scientific about reproducing it at some point.

SDET results are about the same, kernel compile is down a bit on systime
(16-way NUMA-Q)

Kernbench: (make -j vmlinux, maximal tasks)
                              Elapsed      System        User         CPU
               2.5.69-mm7       46.58      117.00      578.47     1492.00
               2.5.69-mm8       46.09      115.11      570.74     1487.25

      1004     2.0% default_idle
       272     8.3% __copy_from_user_ll
       129     1.7% __d_lookup
        79     7.5% link_path_walk
...
       -50    -1.3% find_get_page
       -55    -1.5% zap_pte_range
       -66    -6.5% file_move
       -74    -1.2% page_add_rmap
       -80    -0.6% do_anonymous_page
      -110    -6.9% schedule
      -139    -7.0% atomic_dec_and_lock
      -698    -0.4% total
     -1139    -4.6% page_remove_rmap

Not sure quite what that's all about, but there it is ;-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-05-23  6:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  9:16 2.5.69-mm8 Andrew Morton
2003-05-22 12:05 ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:07 ` 2.5.69-mm8 Helge Hafting
2003-05-22 21:21   ` 2.5.69-mm8 Rudmer van Dijk
2003-05-22 14:55 ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 17:13 ` 2.5.69-mm8 Alexander Hoogerhuis
2003-05-22 18:53 ` 2.5.69-mm8 Felipe Alfaro Solana
2003-05-22 19:30   ` 2.5.69-mm8 Paul Larson
2003-05-22 19:39     ` 2.5.69-mm8 Martin J. Bligh
2003-05-22 19:49       ` 2.5.69-mm8 Paul Larson
2003-05-22 21:03       ` 2.5.69-mm8 Dave Hansen
2003-05-22 20:14     ` 2.5.69-mm8 Andrew Morton
2003-05-22 21:19       ` 2.5.69-mm8 Paul Larson
2003-05-23  6:18 ` Martin J. Bligh [this message]
2003-05-23  7:03   ` 2.5.69-mm8 Dave Hansen
2003-05-23 14:32     ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:02       ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:31   ` 2.5.69-mm8 Martin J. Bligh

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='17990000.1053670694@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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