linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Nick Piggin <npiggin@suse.de>, Rik van Riel <riel@redhat.com>,
	Anton Altaparmakov <aia21@cam.ac.uk>,
	Suparna Bhattacharya <suparna@in.ibm.com>,
	Christoph Hellwig <hch@infradead.org>,
	Zach Brown <zach.brown@oracle.com>,
	Hugh Dickins <hugh@veritas.com>,
	Jared Hulbert <jaredeh@gmail.com>,
	Chris Mason <chris.mason@oracle.com>, David Chinner <dgc@sgi.com>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Neil Brown <neilb@suse.de>, Joern Engel <joern@logfs.org>,
	Miklos Szeredi <miklos@szeredi.hu>, Mingming Cao <cmm@us.ibm.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: vm/fs meetup details
Date: Sat, 7 Jul 2007 12:45:35 +0200	[thread overview]
Message-ID: <20070707104534.GA5686@lazybastard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707061339100.24812@schroedinger.engr.sgi.com>

On Fri, 6 July 2007 13:40:03 -0700, Christoph Lameter wrote:
> 
> An interesting topic is certainly
> 
> 1. Large buffer support
> 
> 2. icache/dentry/buffer_head defragmentation.

Oh certainly!  I should dust off my dcache_static patch.  Some dentries
are hands-off for the shrinker, basically mountpoints and tmpfs.  The
patch moves those to a seperate slab cache.

Jörn

-- 
Data dominates. If you've chosen the right data structures and organized
things well, the algorithms will almost always be self-evident. Data
structures, not algorithms, are central to programming.
-- Rob Pike
-
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

  reply	other threads:[~2007-07-07 12:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  4:01 vm/fs meetup details Nick Piggin
2007-07-05 14:32 ` Peter Zijlstra
2007-07-05 17:54 ` Rik van Riel
2007-07-05 20:40   ` Zach Brown
2007-07-05 21:27     ` David Chinner
2007-07-05 21:40       ` Rik van Riel
2007-07-06  2:26         ` Nick Piggin
2007-07-06 10:01           ` David Chinner
2007-07-06 10:26             ` Jörn Engel
2007-07-06 13:42               ` David Chinner
2007-07-06 13:52                 ` Chris Mason
2007-07-06 15:57                   ` Jörn Engel
2007-07-06 15:58                     ` Steven Whitehouse
2007-07-06 23:47                       ` Neil Brown
2007-07-06  2:00   ` Nick Piggin
2007-07-06 20:40     ` Christoph Lameter
2007-07-07 10:45       ` Jörn Engel [this message]
2007-07-08 23:29         ` David Chinner
2007-07-09  0:27           ` Jörn Engel
2007-07-09 15:53             ` Martin Bligh
2007-07-27 14:30 ` Dave Kleikamp

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=20070707104534.GA5686@lazybastard.org \
    --to=joern@logfs.org \
    --cc=aia21@cam.ac.uk \
    --cc=chris.mason@oracle.com \
    --cc=clameter@sgi.com \
    --cc=cmm@us.ibm.com \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=hugh@veritas.com \
    --cc=jaredeh@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@mbligh.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    --cc=suparna@in.ibm.com \
    --cc=trond.myklebust@fys.uio.no \
    --cc=zach.brown@oracle.com \
    /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).