public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org, Arjan Van de Ven <arjanv@redhat.com>
Subject: Re: Linux 2.4.19-pre5-ac2
Date: Thu, 04 Apr 2002 14:30:22 -0800	[thread overview]
Message-ID: <3CACD3FE.1323F721@zip.com.au> (raw)
In-Reply-To: <200204042017.g34KHqv11609@devserv.devel.redhat.com>

Alan Cox wrote:
> 
> ...
> o       Cache more group descriptors on ext2/ext3       (Arjan van de Ven)

[ See below for the rant ]

I'd be interested in knowing what testing was performed, what
workload this addresses, what improvements were observed, etc.

Did anyone consider and/or test removal of the cache altogether,
and adding a touch_buffer() to the backing buffer_head, to allow the
VM to perform the LRU management instead?

Did anyone try leaving the LRU at its current size and seeing if
a touch_buffer() improves the problematic testcase?

If there is indeed a workload which is improved by this patch,
I would like know what it is, please - I would like to see if allowing
the VM to manage the LRU also fixes that workload, because that's
surely better than pinning down 256 kilobytes of memory per mounted
filesystem.

Thanks.




The rant:

Not singling out Arjan; certainly this is not the most egregious
case lately.  But.  Will people please stop sending kernel
patches straight to tree owners without copying the appropriate
mailing list?

There is no benefit in keeping all the other kernel developers
in the dark.  If a patch is not security-related and is not
trivially boring, tree-owners should consider just dropping
the thing if it has not been seen by the other developers.

It's not as if this mailing list is overwhelmed with technical
content, is it?  If people are shy, or are reluctant to disrupt
the social and political ambiance of linux-kernel, there are
other lists, including

	linux-fsdevel@vger.kernel.org
	linux-mm@kvack.org
	netdev@oss.sgi.com
	ext2-devel@lists.sourceforge.net

and of course many others.

-

  parent reply	other threads:[~2002-04-04 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 20:17 Linux 2.4.19-pre5-ac2 Alan Cox
2002-04-04 20:20 ` arjan
2002-04-04 21:00   ` Alan Cox
2002-04-04 22:30 ` Andrew Morton [this message]
2002-04-04 23:01   ` Alan Cox
2002-04-04 23:21 ` Linux 2.4.19-pre5-ac2: 8253xutl.c compile error Eyal Lebedinsky
  -- strict thread matches above, loose matches on Subject: below --
2002-04-04 20:38 Linux 2.4.19-pre5-ac2 Wayne.Brown

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=3CACD3FE.1323F721@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=alan@redhat.com \
    --cc=arjanv@redhat.com \
    --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