From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
fabbione@ubuntu.com, Andrew Morton <akpm@osdl.org>
Subject: Re: VFS nr_files accounting
Date: Tue, 7 Mar 2006 12:11:20 +0530 [thread overview]
Message-ID: <20060307064120.GA5946@in.ibm.com> (raw)
In-Reply-To: <20060306.123904.35238417.davem@davemloft.net>
On Mon, Mar 06, 2006 at 12:39:04PM -0800, David S. Miller wrote:
> From: Dipankar Sarma <dipankar@in.ibm.com>
> Date: Sun, 5 Mar 2006 17:08:47 +0530
>
> > Great. I look forward to hearing from you about the results
> > with your test case.
>
> It works quite fine so far, I haven't seen the filp exhaustion
> nor a highly fragmented filp SLAB.
Good to hear that.
> Instead, I'm not hitting other bugs that are of my own doing
> on Niagara, which is what I wanted to accomplish with these
> stress tests in the first place :-)
Not good :)
> I think we should seriously consider these patches for 2.6.16
Isn't it a little too late in the 2.6.16 cycle ? I would have
liked a little more time in -mm. Anyway, it is Linus' call.
I can refresh the patches and submit against latest mainline
if Linus and Andrew want.
Thanks
Dipankar
next prev parent reply other threads:[~2006-03-07 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 10:25 VFS nr_files accounting David S. Miller
2006-03-04 14:17 ` Dipankar Sarma
2006-03-04 22:22 ` David S. Miller
2006-03-04 22:28 ` David S. Miller
2006-03-04 22:32 ` David S. Miller
2006-03-05 7:05 ` Dipankar Sarma
2006-03-05 7:37 ` David S. Miller
2006-03-05 11:38 ` Dipankar Sarma
2006-03-06 20:39 ` David S. Miller
2006-03-07 6:41 ` Dipankar Sarma [this message]
2006-03-07 6:47 ` David S. Miller
2006-03-07 8:02 ` Dipankar Sarma
2006-03-07 6:53 ` Nick Piggin
2006-03-07 7:00 ` David S. Miller
2006-03-07 8:09 ` Dipankar Sarma
2006-03-07 8:55 ` Fabio Massimo Di Nitto
2006-03-07 7:06 ` Andrew Morton
2006-03-07 12:09 ` Dipankar Sarma
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=20060307064120.GA5946@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=fabbione@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.