From: Christoph Hellwig <hch@sgi.com>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.5.50-mm2
Date: Fri, 13 Dec 2002 17:55:26 -0500 [thread overview]
Message-ID: <20021213175526.C2581@sgi.com> (raw)
In-Reply-To: <3DF453C8.18B24E66@digeo.com>; from akpm@digeo.com on Mon, Dec 09, 2002 at 12:26:48AM -0800
On Mon, Dec 09, 2002 at 12:26:48AM -0800, Andrew Morton wrote:
> +remove-PF_SYNC.patch
>
> remove the current->flags:PF_SYNC abomination. Adds a `sync' arg to
> all writepage implementations to tell them whether they are being
> called for memory cleansing or for data integrity.
Any chance you could pass down a struct writeback_control instead of
just the sync flag? XFS always used ->writepage similar to the
->vm_writeback in older kernel releases because writing out more
than one page of delalloc space is really needed to be efficient and
this would allow us to get a few more hints about the VM's intentions.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@sgi.com>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.5.50-mm2
Date: Fri, 13 Dec 2002 17:55:26 -0500 [thread overview]
Message-ID: <20021213175526.C2581@sgi.com> (raw)
In-Reply-To: <3DF453C8.18B24E66@digeo.com>; from akpm@digeo.com on Mon, Dec 09, 2002 at 12:26:48AM -0800
On Mon, Dec 09, 2002 at 12:26:48AM -0800, Andrew Morton wrote:
> +remove-PF_SYNC.patch
>
> remove the current->flags:PF_SYNC abomination. Adds a `sync' arg to
> all writepage implementations to tell them whether they are being
> called for memory cleansing or for data integrity.
Any chance you could pass down a struct writeback_control instead of
just the sync flag? XFS always used ->writepage similar to the
->vm_writeback in older kernel releases because writing out more
than one page of delalloc space is really needed to be efficient and
this would allow us to get a few more hints about the VM's intentions.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-12-13 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 8:26 2.5.50-mm2 Andrew Morton
2002-12-09 8:26 ` 2.5.50-mm2 Andrew Morton
2002-12-13 22:55 ` Christoph Hellwig [this message]
2002-12-13 22:55 ` 2.5.50-mm2 Christoph Hellwig
2002-12-13 19:58 ` 2.5.50-mm2 Andrew Morton
2002-12-13 19:58 ` 2.5.50-mm2 Andrew Morton
[not found] ` <200212092059.06287.tomlins@cam.org>
[not found] ` <3DF54BD7.726993D@digeo.com>
2003-02-05 4:41 ` [PATCH] let kernel find QT in latest debian sid Ed Tomlinson
2003-02-11 13:13 ` [BUG] link error in usbserial with gcc3.2 Ed Tomlinson
2003-02-12 1:59 ` Ed Tomlinson
2003-02-18 5:51 ` Greg KH
2003-02-18 12:50 ` Ed Tomlinson
2003-02-13 13:18 ` [PATCH] (0-2) governors for 60-bk Ed Tomlinson
2003-02-14 21:38 ` [PATCH] CFQ scheduler, #2 Ed Tomlinson
2003-02-15 8:33 ` Jens Axboe
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=20021213175526.C2581@sgi.com \
--to=hch@sgi.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.