mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Bart Samwel <bart@samwel.tk>
Cc: smackinlay@mail.com, linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] laptop-mode-2.6.0, version 5
Date: Fri, 2 Jan 2004 13:05:43 -0800	[thread overview]
Message-ID: <20040102130543.36f61809.akpm@osdl.org> (raw)
In-Reply-To: <3FF56BC6.50201@samwel.tk>

Bart Samwel <bart@samwel.tk> wrote:
>
> Find attached version 5 of the laptop-mode patch. It includes the 
> following changes:
> 
> * Fix for supporting 64-bit sector_t (thanks hugang!)

%Lu expects an unsigned long long argument and nothing else, so we should
cast this sector_t to unsigned long long, not u64.

With u64 this code will generate a warning on ppc64 (at least), because
ppc64's u64 is unsigned long.

> * Simplified the design a bit, saved us a timer. It now only wakes up 
> kupdate to write back stuff: kupdate disregards age while laptop_mode is 
> active, so it writes back everything anyway.
> 
> * balance_dirty_pages does it's job again in laptop mode. However, when 
> it decides to write back pages, it now also calls disk_is_spun_up(), 
> which makes sure that the remainder of the dirty pages are written 
> immediately as well. That means that if a writer writes an amount of 
> data that is about 50% of memory, and dirty_ratio is 40%, that the disk 
> will spin up after 4/5ths of the data is written, will write the full 
> 4/5ths of the data at once, and then the disk can spin down again 
> because the remaining 10% will be not be written until the next spin-up.

hum, OK, I'll tkae a look at that, thanks.

> * The control script now sets dirty_background_ratio to the same value 
> as dirty_ratio, so that background writes are effectively disabled. This 
> enables a writer to fill up up to dirty_ratio (default 40%) of the 
> memory with dirty blocks before the disk is spun up.
> 
> * Includes control script (scripts/laptop_mode).
>
> * Includes docs (Documentation/laptop-mode.txt).

Can you please place the control script inside laptop-mode.txt rather than
in scripts/?  The scripts directory is for kernel build tools, not for
kernel runtime support things.

Thanks.

  reply	other threads:[~2004-01-02 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040102025509.91753.qmail@mail.com>
2004-01-02 13:01 ` Bart Samwel
2004-01-02 21:05   ` Andrew Morton [this message]
     [not found] <20031231210756.315.qmail@mail.com>
     [not found] ` <3FF3887C.90404@samwel.tk>
     [not found]   ` <20031231184830.1168b8ff.akpm@osdl.org>
     [not found]     ` <3FF43BAF.7040704@samwel.tk>
     [not found]       ` <3FF457C0.2040303@samwel.tk>
     [not found]         ` <20040101183545.GD5523@suse.de>
2004-01-02  9:02           ` [PATCH] laptop-mode-2.6.0 " Hugang
2004-01-02 11:27             ` Jens Axboe
2004-01-02 11:38               ` Hugang
2004-01-02 12:03                 ` Jens Axboe
2004-01-04  9:52                   ` Peter Chubb
2004-01-04 10:31                     ` Jens Axboe
2004-03-29 15:42                     ` Jens Axboe
2004-03-29 15:42                   ` Peter Chubb

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=20040102130543.36f61809.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=bart@samwel.tk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smackinlay@mail.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

Powered by JetHome