From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mark Lord <kernel@teksavvy.com>
Cc: Nigel Cunningham <nigel@tuxonice.net>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.35 Regression: Ages spent discarding blocks that weren't used!
Date: Wed, 04 Aug 2010 14:02:10 -0400 [thread overview]
Message-ID: <yq17hk6qmsd.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4C5960B0.7020003@teksavvy.com> (Mark Lord's message of "Wed, 04 Aug 2010 08:44:32 -0400")
>>>>> "Mark" == Mark Lord <kernel@teksavvy.com> writes:
Mark> Looks to me like more and more things are using the block discard
Mark> functionality, and as predicted it is slowing things down
Mark> enormously.
Mark> The problem is that we still only discard tiny bits (a single
Mark> range still??) per TRIM command, rather than batching larger
Mark> ranges and larger numbers of ranges into single TRIM commands.
Mark> That's a very poor implementation, especially when things start
Mark> enabling it by default. Eg. the swap code, mke2fs, etc..
I'm working on aggregation. But it's harder than we initially
thought...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2010-08-04 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 1:40 2.6.35 Regression: Ages spent discarding blocks that weren't used! Nigel Cunningham
2010-08-04 8:59 ` Stefan Richter
2010-08-04 9:16 ` Nigel Cunningham
2010-08-04 12:44 ` Mark Lord
2010-08-04 18:02 ` Martin K. Petersen [this message]
2010-08-04 21:22 ` Nigel Cunningham
2010-08-05 3:58 ` Hugh Dickins
2010-08-05 6:28 ` Nigel Cunningham
2010-08-06 1:15 ` Hugh Dickins
2010-08-06 4:40 ` Nigel Cunningham
2010-08-06 22:07 ` Hugh Dickins
2010-08-07 22:47 ` Nigel Cunningham
2010-08-13 11:54 ` Christoph Hellwig
2010-08-13 18:15 ` Hugh Dickins
2010-08-14 11:43 ` Christoph Hellwig
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=yq17hk6qmsd.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@tuxonice.net \
/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