mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange performance change 59 -> 61/62
Date: Wed, 19 Feb 2003 10:19:57 -0800	[thread overview]
Message-ID: <20030219101957.05088aa1.akpm@digeo.com> (raw)
In-Reply-To: <32720000.1045671824@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> I'm comparing 59-mjb6 to 61-mjb1 and notice some strange performance
> differences that I can't explain ... not a big drop, but odd.
>...
> 
> 1562 .text.lock.file_table
> 583 dentry_open
> 551 get_empty_filp

The first one here is fget().  That's causing problems on ppc64 as well - the
machine is spending as long in fget as it is in copy_foo_user() in dbench
runs.

One possibility is that we're calling fget() more often than previously,
although that would be rather odd.  Can you add the below patch, and monitor
/proc/meminfo:nr_fgets?

If not that, then maybe some funny cacheline aliasing thing?


 file_table.c       |    2 ++
 linux/page-flags.h |    1 +
 page_alloc.c       |    1 +
 3 files changed, 4 insertions(+)

diff -puN include/linux/page-flags.h~fget-counter include/linux/page-flags.h
--- 25/include/linux/page-flags.h~fget-counter	2003-02-19 10:14:54.000000000 -0800
+++ 25-akpm/include/linux/page-flags.h	2003-02-19 10:15:26.000000000 -0800
@@ -87,6 +87,7 @@ struct page_state {
 	unsigned long nr_reverse_maps;	/* includes PageDirect */
 	unsigned long nr_mapped;	/* mapped into pagetables */
 	unsigned long nr_slab;		/* In slab */
+	unsigned long nr_fgets;
 #define GET_PAGE_STATE_LAST nr_slab
 
 	/*
diff -puN mm/page_alloc.c~fget-counter mm/page_alloc.c
--- 25/mm/page_alloc.c~fget-counter	2003-02-19 10:15:20.000000000 -0800
+++ 25-akpm/mm/page_alloc.c	2003-02-19 10:15:48.000000000 -0800
@@ -1439,6 +1439,7 @@ static char *vmstat_text[] = {
 	"nr_reverse_maps",
 	"nr_mapped",
 	"nr_slab",
+	"nr_fgets",
 
 	"pgpgin",
 	"pgpgout",
diff -puN fs/file_table.c~fget-counter fs/file_table.c
--- 25/fs/file_table.c~fget-counter	2003-02-19 10:15:55.000000000 -0800
+++ 25-akpm/fs/file_table.c	2003-02-19 10:16:21.000000000 -0800
@@ -12,6 +12,7 @@
 #include <linux/module.h>
 #include <linux/smp_lock.h>
 #include <linux/fs.h>
+#include <linux/mm.h>
 #include <linux/security.h>
 #include <linux/eventpoll.h>
 #include <linux/mount.h>
@@ -156,6 +157,7 @@ struct file * fget(unsigned int fd)
 	struct file * file;
 	struct files_struct *files = current->files;
 
+	inc_page_state(nr_fgets);
 	read_lock(&files->file_lock);
 	file = fcheck(fd);
 	if (file)

_


  reply	other threads:[~2003-02-19 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 16:23 Martin J. Bligh
2003-02-19 18:19 ` Andrew Morton [this message]
2003-02-21  7:19   ` Martin J. Bligh
2003-02-21  7:28     ` Martin J. Bligh
2003-02-21  7:45       ` Andrew Morton
2003-02-21 17:27         ` Martin J. Bligh
2003-02-21 20:20           ` Andrew Morton
2003-02-22  7:46             ` Martin J. Bligh
2003-02-22  8:04               ` Andrew Morton
2003-02-22  8:10                 ` Martin J. Bligh
2003-02-19 17:19 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=20030219101957.05088aa1.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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®