From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org,
torvalds@osdl.org, fabbione@ubuntu.com, akpm@osdl.org
Subject: Re: VFS nr_files accounting
Date: Tue, 7 Mar 2006 13:39:22 +0530 [thread overview]
Message-ID: <20060307080922.GC5946@in.ibm.com> (raw)
In-Reply-To: <20060306.230030.131765838.davem@davemloft.net>
On Mon, Mar 06, 2006 at 11:00:30PM -0800, David S. Miller wrote:
> From: Nick Piggin <nickpiggin@yahoo.com.au>
> Date: Tue, 07 Mar 2006 17:53:14 +1100
>
> > The other thing that is typically done for regressions like these
> > close to release time is to revert the offending changes. I figure
> > that in this case, such an option is probably _more_ risky.
>
> Especially since we're talking about something that went into
> 2.6.14
Without a doubt, yes. Waaaay more risky. Compared to that the
rcu-batch-tuning and fix-file-counting are a cakewalk. It would
however be nice if Christoph or Viro gives the file counting
patch a look-over just so that I didn't break any sysctl
stuff.
Thanks
Dipankar
next prev parent reply other threads:[~2006-03-07 8:10 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
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 [this message]
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=20060307080922.GC5946@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=nickpiggin@yahoo.com.au \
--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.