From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, suparna@in.ibm.com
Subject: Re: [PATCH] Writeback page range hint
Date: Tue, 24 Aug 2004 02:07:23 +0100 [thread overview]
Message-ID: <20040824010723.GA15668@redhat.com> (raw)
In-Reply-To: <200408232138.i7NLcfJd019125@hera.kernel.org>
On Mon, Aug 23, 2004 at 07:59:27PM +0000, Linux Kernel wrote:
> ChangeSet 1.2034, 2004/08/23 12:59:27-07:00, akpm@osdl.org
>
> [PATCH] Writeback page range hint
>
> Modify mpage_writepages to optionally only write back dirty pages within a
> specified range in a file (as in the case of O_SYNC). Cheat a little to avoid
> changes to prototypes of aops - just put the <start, end> hint into the
> writeback_control struct instead. If <start, end> are not set, then default
> to writing back all the mapping's dirty pages.
FYI, this chunk...
> long pages_skipped; /* Pages which were not written */
> - int nonblocking; /* Don't get stuck on request queues */
> - int encountered_congestion; /* An output: a queue is full */
> - int for_kupdate; /* A kupdate writeback */
> - int for_reclaim; /* Invoked from the page allocator */
> +
> + /*
> + * For a_ops->writepages(): is start or end are non-zero then this is
> + * a hint that the filesystem need only write out the pages inside that
> + * byterange. The byte at `end' is included in the writeout request.
> + */
> + loff_t start;
> + loff_t end;
> +
> + int nonblocking:1; /* Don't get stuck on request queues */
> + int encountered_congestion:1; /* An output: a queue is full */
> + int for_kupdate:1; /* A kupdate writeback */
> + int for_reclaim:1; /* Invoked from the page allocator */
Causes sparse spew..
include/linux/writeback.h:54:19: warning: dubious one-bit signed bitfield
include/linux/writeback.h:55:30: warning: dubious one-bit signed bitfield
include/linux/writeback.h:56:19: warning: dubious one-bit signed bitfield
include/linux/writeback.h:57:19: warning: dubious one-bit signed bitfield
Dave
next parent reply other threads:[~2004-08-24 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408232138.i7NLcfJd019125@hera.kernel.org>
2004-08-24 1:07 ` Dave Jones [this message]
2004-08-24 1:14 ` [PATCH] Writeback page range hint Andrew Morton
2004-08-24 1:18 ` Dave Jones
2004-08-24 1:21 ` Andrew Morton
2004-08-24 1:29 ` wli
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=20040824010723.GA15668@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.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