From: Andrea Arcangeli <andrea@suse.de>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre5aa1 and splitted vm-33
Date: Tue, 16 Apr 2002 16:47:48 +0200 [thread overview]
Message-ID: <20020416164748.C29747@dualathlon.random> (raw)
In-Reply-To: <20020331164815.A1331@dualathlon.random> <20020406170703.A32084@infradead.org>
On Sat, Apr 06, 2002 at 05:07:03PM +0100, Christoph Hellwig wrote:
> > Only in 2.4.19pre5aa1: 20_kiobuf-slab-2
> >
> > Other patch from Chuck Lever to allocate the whole kiobuf from slab,
> > using pointer to arrays, to have small structures not larger
> > than one page (that would otherwise become sensitive to
> > physical ram page granular fragmentation). While auditing and
> > merging the patch I also did various small fixes, so please rely
> > on this patch as a final version, because the original one had a few
> > bugs/leftovers.
>
> What is the reason for adding kio_ prefixes to the 'blocks' and 'bh' members
> of struct kiobuf? - These fields haven't any new semantics at all, but that
> change increases the delta dramatically.
just a grep feature. Chuck did it and I liked it.
> > Merged various fixes, in particular delayed writes should now be
> > really flushed by the VM, previously the fact the vm holds
> > the page lock was forbidding that. New logic is much cleaner too.
>
> Do you plan to submit the XFS delalloc changes back to SGI?
They came from the xfs tree actually, so we should be in sync.
Andrea
prev parent reply other threads:[~2002-04-16 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 14:48 Andrea Arcangeli
2002-03-31 18:10 ` Christoph Hellwig
2002-03-31 18:38 ` Andrea Arcangeli
2002-03-31 19:00 ` Christoph Hellwig
2002-04-01 0:04 ` Andrea Arcangeli
2002-04-06 16:07 ` Christoph Hellwig
2002-04-16 14:47 ` Andrea Arcangeli [this message]
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=20020416164748.C29747@dualathlon.random \
--to=andrea@suse.de \
--cc=hch@infradead.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
all inboxes | Powered by JetHome®