All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 86471] drastic reduction of write performance after the termination of mysqld
Date: Thu, 23 Oct 2014 16:36:01 +0000	[thread overview]
Message-ID: <bug-86471-13602-ApLc0iLpJM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86471-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=86471

--- Comment #6 from Markus Königshaus <m.koenigshaus@wut.de> ---

I think I have found the error. The kernel calls apparently for the same page
dec_zone_page_state on (page, NR_FILE_DIRTY) twice, which means that the dirty
page counter underflows (is getting negative): 

cat /proc/meminfo 
MemTotal:         511492 kB
MemFree:          406972 kB
MemAvailable:     450536 kB
Buffers:            1840 kB
Cached:            52140 kB
SwapCached:            0 kB
Active:            54348 kB
Inactive:          34456 kB
Active(anon):      34904 kB
Inactive(anon):     5440 kB
Active(file):      19444 kB
Inactive(file):    29016 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:             0 kB
HighFree:              0 kB
LowTotal:         511492 kB
LowFree:          406972 kB
SwapTotal:             0 kB
SwapFree:              0 kB
>> Dirty:          4294967148 kB
Writeback:             0 kB
AnonPages:         34844 kB
Mapped:            13992 kB
Shmem:              5520 kB
Slab:               9196 kB
SReclaimable:       4976 kB
SUnreclaim:         4220 kB
KernelStack:         696 kB
PageTables:         1024 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      255744 kB
Committed_AS:     365452 kB
VmallocTotal:     499712 kB
VmallocUsed:        3512 kB
VmallocChunk:     495964 kB

The writeback - mechanism thinks that too much pages are dirty and disables the
writeback - cache.

Who can I send this bug?
Markus

-- 
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-10-23 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 13:14 [Bug 86471] New: drastic reduction of write performance after the termination of mysqld bugzilla-daemon
2014-10-17 16:10 ` [Bug 86471] " bugzilla-daemon
2014-10-17 16:29 ` bugzilla-daemon
2014-10-22 16:00 ` bugzilla-daemon
2014-10-22 20:22 ` bugzilla-daemon
2014-10-23 10:34 ` bugzilla-daemon
2014-10-23 16:36 ` bugzilla-daemon [this message]
2014-10-24 15:14 ` bugzilla-daemon
2014-10-24 15:34 ` bugzilla-daemon
2014-11-13 14:24 ` bugzilla-daemon
2014-11-13 14:33 ` bugzilla-daemon
2014-11-13 14:41 ` bugzilla-daemon

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=bug-86471-13602-ApLc0iLpJM@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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.