All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <fsdeveloper@yahoo.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: pdflush -> noflushd related question
Date: Sat, 31 May 2003 20:36:55 +0200	[thread overview]
Message-ID: <200305312036.55506.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <20030531105850.7cc92601.akpm@digeo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 31 May 2003 19:58, Andrew Morton wrote:
> You can turn these guys off by setting the sysctls to 1000000000
> I guess.   Problem is, I don't think there's a way of starting them
> again until the ten million seconds expires.  hmm.

I've thought a little bit more about it.
Why do you think, there is no way of waking up?
Is it, because, when I set it to 1000000000 and the back to,
let's say, 500, the pdflush threads don't wake up to recognize
this change? Is this the cause?

What about signaling all pdflush threads with, for example,
for(ALL_PDFLUSHS)
	kill(pid, SIGSTOP);

Don't they wake up then and recognize the reducing of the timeout?
The old noflushd did so to wake up updated.

thanks.

- -- 
Regards Michael Büsch
http://www.8ung.at/tuxsoft
 20:32:32 up  6:04,  2 users,  load average: 2.05, 2.03, 2.00

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+2PZHoxoigfggmSgRAjx2AJ9orNNk8SLQlhBg+lJ1ZsyGgOb/9ACgjBjW
bm0WPZwvb8Rd0bGti2XFBOQ=
=Et8g
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-05-31 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 16:41 pdflush -> noflushd related question Michael Buesch
2003-05-31 17:58 ` Andrew Morton
2003-05-31 18:24   ` Michael Buesch
2003-05-31 18:36   ` Michael Buesch [this message]
2003-05-31 18:42     ` Andrew Morton

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=200305312036.55506.fsdeveloper@yahoo.de \
    --to=fsdeveloper@yahoo.de \
    --cc=akpm@digeo.com \
    --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 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.