mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Pfiffer <andyp@osdl.org>
To: Andrew Morton <akpm@digeo.com>
Cc: christophe@saout.de, adam@yggdrasil.com, linux-kernel@vger.kernel.org
Subject: Re: ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem?
Date: 12 Jun 2003 10:27:36 -0700	[thread overview]
Message-ID: <1055438856.1202.6.camel@andyp.pdx.osdl.net> (raw)
In-Reply-To: <20030611172958.5e4d3500.akpm@digeo.com>

On Wed, 2003-06-11 at 17:29, Andrew Morton wrote:
> Andy Pfiffer <andyp@osdl.org> wrote:
> >
> > So now the important question: is it wrong to not sync_blockdev() until
> > the count drops to 0?
> 
> Should be OK.  The close will not sync anything if someone else has the
> blockdev open (ie: there's a filesystem mounted there).
> 
> But sync() should certainly write everything out, and lilo does perform a
> sync.
> 
> I'd be interested in seeing the contents of /proc/meminfo immediately after
> the lilo run, see if there's any dirty memory left around.

How I measured:

	# cat measure
	#!/bin/sh
	sync
	cat /proc/meminfo
	/sbin/lilo
	cat /proc/meminfo

	# ./measure | dd bs=1024k > out

2.5.68 pure:

Before:				After:
MemTotal:       514304 kB	MemTotal:       514304 kB
MemFree:        388720 kB	MemFree:        385648 kB
Buffers:         10056 kB	Buffers:         12092 kB
Cached:          54000 kB	Cached:          54956 kB
SwapCached:          0 kB	SwapCached:          0 kB
Active:          62928 kB	Active:          63240 kB
Inactive:        34416 kB	Inactive:        37120 kB
HighTotal:           0 kB	HighTotal:           0 kB
HighFree:            0 kB	HighFree:            0 kB
LowTotal:       514304 kB	LowTotal:       514304 kB
LowFree:        388720 kB	LowFree:        385648 kB
SwapTotal:      787144 kB	SwapTotal:      787144 kB
SwapFree:       787144 kB	SwapFree:       787144 kB
Dirty:               0 kB	Dirty:               8 kB <---
Writeback:           0 kB	Writeback:           0 kB
Mapped:          45484 kB	Mapped:          45488 kB
Slab:            11880 kB	Slab:            12100 kB
Committed_AS:   146184 kB	Committed_AS:   146184 kB
PageTables:        656 kB	PageTables:        656 kB
VmallocTotal:   516040 kB	VmallocTotal:   516040 kB
VmallocUsed:     42608 kB	VmallocUsed:     42608 kB
VmallocChunk:   473432 kB	VmallocChunk:   473432 kB

2.5.68+kludge:

Before:				After:
MemTotal:       514304 kB	MemTotal:       514304 kB
MemFree:        390416 kB	MemFree:        387216 kB
Buffers:          9844 kB	Buffers:         11892 kB
Cached:          52920 kB	Cached:          53864 kB
SwapCached:          0 kB	SwapCached:          0 kB
Active:          62136 kB	Active:          62452 kB
Inactive:        33908 kB	Inactive:        36600 kB
HighTotal:           0 kB	HighTotal:           0 kB
HighFree:            0 kB	HighFree:            0 kB
LowTotal:       514304 kB	LowTotal:       514304 kB
LowFree:        390416 kB	LowFree:        387216 kB
SwapTotal:      787144 kB	SwapTotal:      787144 kB
SwapFree:       787144 kB	SwapFree:       787144 kB
Dirty:               0 kB	Dirty:               4 kB <---
Writeback:           0 kB	Writeback:           0 kB
Mapped:          45448 kB	Mapped:          45452 kB
Slab:            11564 kB	Slab:            11756 kB
Committed_AS:   146192 kB	Committed_AS:   146132 kB
PageTables:        656 kB	PageTables:        656 kB
VmallocTotal:   516040 kB	VmallocTotal:   516040 kB
VmallocUsed:     42608 kB	VmallocUsed:     42608 kB
VmallocChunk:   473432 kB	VmallocChunk:   473432 kB





  parent reply	other threads:[~2003-06-12 17:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 19:04 [KEXEC][2.5.69] kexec for 2.5.69 available Andy Pfiffer
2003-05-09 20:04 ` ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69 available) Christophe Saout
2003-05-09 20:55   ` Andy Pfiffer
2003-05-09 20:46     ` ext3/lilo/2.5.6[89] (was: [KEXEC][2.5.69] kexec for 2.5.69available) Riley Williams
2003-05-09 22:39       ` Joe Korty
2003-05-09 23:39       ` Andy Pfiffer
2003-06-11 22:08     ` ext[23]/lilo/2.5.{68,69,70} -- IDE Problem? Andy Pfiffer
2003-06-11 23:21       ` Christophe Saout
2003-06-11 23:40         ` Bartlomiej Zolnierkiewicz
2003-06-12  0:20         ` ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem? Andy Pfiffer
2003-06-12  0:29           ` Andrew Morton
2003-06-12 10:42             ` Christophe Saout
2003-06-12 10:54               ` Andrew Morton
2003-06-12 11:12                 ` Christophe Saout
2003-06-12 11:24                 ` ext[23]/lilo/2.5.{68,69,70} -- strace lilo - freeze Christophe Saout
2003-06-12 12:44                 ` ext[23]/lilo/2.5.{68,69,70} -- blkdev_put() problem? Herbert Xu
2003-06-12 17:27             ` Andy Pfiffer [this message]
2003-06-12 17:53               ` Andrew Morton
2003-06-12 18:03                 ` Andy Pfiffer
2003-06-12 18:10                   ` Andrew Morton
2003-06-12 18:53                     ` Christophe Saout
2003-06-12 18:25                   ` Andy Pfiffer
2003-06-13  8:01                     ` Andrew Morton
2003-06-13  9:57                       ` Herbert Xu
2003-06-13 14:42                       ` Eduardo Pereira Habkost
2003-06-13 17:17                       ` Andy Pfiffer
2003-06-13 22:12                       ` Unai Garro Arrazola
2003-06-13 22:28                         ` 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=1055438856.1202.6.camel@andyp.pdx.osdl.net \
    --to=andyp@osdl.org \
    --cc=adam@yggdrasil.com \
    --cc=akpm@digeo.com \
    --cc=christophe@saout.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®