All of lore.kernel.org
 help / color / mirror / Atom feed
From: wcheng@sourceware.org <wcheng@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs super.c
Date: 6 Feb 2007 22:08:37 -0000	[thread overview]
Message-ID: <20070206220837.7587.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	wcheng at sourceware.org	2007-02-06 22:08:37

Modified files:
	gfs-kernel/src/gfs: super.c 

Log message:
	Bugzilla 220622:
	
	Allow vmalloc in stat_gfs_async() (as in RHEL5) to alleviate statfs
	performance issue. This should allow statfs_slot tunable to take
	more asynchronous locks. Hopefully "df" and "ls" could run a little
	bit faster with this.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/super.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.12.2.6&r2=1.12.2.7

--- cluster/gfs-kernel/src/gfs/super.c	2007/01/22 07:43:52	1.12.2.6
+++ cluster/gfs-kernel/src/gfs/super.c	2007/02/06 22:08:36	1.12.2.7
@@ -18,6 +18,7 @@
 #include <asm/semaphore.h>
 #include <linux/completion.h>
 #include <linux/buffer_head.h>
+#include <linux/vmalloc.h>
 
 #include "gfs.h"
 #include "dio.h"
@@ -841,7 +842,7 @@
 
 	memset(sg, 0, sizeof(struct gfs_stat_gfs));
 
-	gha = kmalloc(slots * sizeof(struct gfs_holder), GFP_KERNEL);
+	gha = vmalloc(slots * sizeof(struct gfs_holder));
 	if (!gha)
 		return -ENOMEM;
 	memset(gha, 0, slots * sizeof(struct gfs_holder));
@@ -885,7 +886,7 @@
 		yield();
 	}
 
-	kfree(gha);
+	vfree(gha);
 
 	return error;
 }



             reply	other threads:[~2007-02-06 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06 22:08 wcheng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-20  4:45 [Cluster-devel] cluster/gfs-kernel/src/gfs super.c wcheng
2006-08-09 20:28 rpeterso
2006-08-02  1:37 wcheng
2006-08-02  1:28 wcheng

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=20070206220837.7587.qmail@sourceware.org \
    --to=wcheng@sourceware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.