From: Bernhard Heidegger <bheide@hyperwave.com>
To: Zlatko.Calusic@CARNet.hr
Cc: "H. Peter Anvin" <hpa@transmeta.com>,
Linux Kernel List <linux-kernel@vger.rutgers.edu>,
Linux-MM List <linux-mm@kvack.org>
Subject: Re: [PATCH] 498+ days uptime
Date: Thu, 27 Aug 1998 14:07:32 +0200 (MET DST) [thread overview]
Message-ID: <199808271207.OAA15842@hwal02.hyperwave.com> (raw)
In-Reply-To: <87ww7v73zg.fsf@atlas.CARNet.hr>
>>>>> ">" == Zlatko Calusic <Zlatko.Calusic@CARNet.hr> writes:
>> "H. Peter Anvin" <hpa@transmeta.com> writes:
>> >
>> > bdflush yes, but update is not obsolete.
>> >
>> > It is still needed if you want to make sure data (and metadata)
>> > eventually gets written to disk.
>> >
>> > Of course, you can run without update, but then don't bother if you
>> > lose file in system crash, even if you edited it and saved it few
>> > hours ago. :)
>> >
>> > Update is very important if you have lots of RAM in your computer.
>> >
>>
>> Oh. I guess my next question then is "why", as why can't this be done
>> by kflushd as well?
>>
>> To tell you the truth, I'm not sure why, these days.
>> I thought it was done this way (update running in userspace) so to
>> have control how often buffers get flushed. But, I believe bdflush
>> program had this functionality, and it is long gone (as you correctly
>> noticed).
IMHO, update/bdflush (in user space) calls sys_bdflush regularly. This
function (fs/buffer.c) calls sync_old_buffers() which itself sync_supers
and sync_inodes before it goes through the dirty buffer lust (to write
some dirty buffers); the kflushd only writes some dirty buffers dependent
on the sysctl parameters.
If I'm wrong, please feel free to correct me!
Regards
Bernhard
get my pgp key from a public keyserver (keyID=0x62446355)
-----------------------------------------------------------------------------
Bernhard Heidegger bheide@hyperwave.com
Hyperwave Software Research & Development
Schloegelgasse 9/1, A-8010 Graz
Voice: ++43/316/820918-25 Fax: ++43/316/820918-99
-----------------------------------------------------------------------------
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-08-27 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199808262153.OAA13651@cesium.transmeta.com>
1998-08-26 22:49 ` [PATCH] 498+ days uptime Zlatko Calusic
1998-08-27 12:07 ` Bernhard Heidegger [this message]
1998-08-27 12:21 ` Zlatko Calusic
1998-08-27 12:43 ` Bernhard Heidegger
1998-08-28 1:03 ` Eric W. Biederman
1998-08-28 9:09 ` Bernhard Heidegger
1998-08-28 13:14 ` Eric W. Biederman
1998-08-28 16:03 ` Bernhard Heidegger
1998-08-28 22:03 ` Zlatko Calusic
1998-08-31 8:32 ` Bernhard Heidegger
1998-08-28 21:47 ` Zlatko Calusic
1998-08-28 21:36 ` Zlatko Calusic
1998-08-28 21:32 ` Zlatko Calusic
1998-08-28 9:35 ` Stephen C. Tweedie
1998-08-28 22:16 ` Zlatko Calusic
1998-08-30 15:10 ` Stephen C. Tweedie
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=199808271207.OAA15842@hwal02.hyperwave.com \
--to=bheide@hyperwave.com \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.rutgers.edu \
--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.