From: Balbir Singh <balbir@in.ibm.com>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Per-superblock unused dentry LRU lists V2
Date: Thu, 25 May 2006 09:36:04 +0530 [thread overview]
Message-ID: <20060525040604.GB25185@in.ibm.com> (raw)
In-Reply-To: <20060524110001.GU1331387@melbourne.sgi.com>
> +/*
> + * Shrink the dentry LRU on æ given superblock.
^^^
This character (ae) looks strange.
The other changes look fine. Do you have any performance numbers, any
results from stress tests (for version 2 of the patch)?
Balbir Singh,
Linux Technology Center,
IBM Software Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-05-25 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 11:00 [PATCH] Per-superblock unused dentry LRU lists V2 David Chinner
2006-05-25 4:06 ` Balbir Singh [this message]
2006-05-25 6:15 ` David Chinner
2006-05-25 6:29 ` Balbir Singh
2006-05-25 6:33 ` David Chinner
2006-05-25 6:52 ` Balbir Singh
2006-05-25 8:13 ` David Chinner
2006-05-26 0:24 ` David Chinner
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=20060525040604.GB25185@in.ibm.com \
--to=balbir@in.ibm.com \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).