From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
agk@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: request baset device mapper in Linux
Date: Thu, 8 Sep 2011 15:27:56 +0200 [thread overview]
Message-ID: <20110908132756.GT31717@ics.muni.cz> (raw)
In-Reply-To: <4E367256.8020206@ct.jp.nec.com>
On Mon, Aug 01, 2011 at 06:31:02PM +0900, Kiyoshi Ueda wrote:
> Hi Lukas,
>
> Lukas Hejtmanek wrote:
> > On Sat, Jul 23, 2011 at 04:28:06PM +0900, Jun'ichi Nomura wrote:
> >> As Kiyoshi suggested, it is important to know whether this
> >> problem occurs with the latest kernel.
> >> So if you could try 3.0, it would be very helpful.
> >
> > so, do I need to check recent kernel as the patch works for me?
>
> Yes, please.
> (Unfortunately my storage has been broken today :-<)
>
> CPU usage seems to be one of the reasons for your case, but I
> still cannot understand why memory pressure is needed.
> I want to know your problem also occurs on 3.0 without the patch.
Well, I tried 3.0.3 kernel. It is not so bad as 2.6.32.36, but it is not as
good as the same kernel with your patch.
CPU load is caused by ksoftirqd (30-40%) and kworker (30%).
Overal speed is about 2.5GB/s. With your patch I can reach 2.8-2.9GB/s.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2011-09-08 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 8:26 Lukas Hejtmanek
2011-07-21 11:11 ` Kiyoshi Ueda
2011-07-21 13:26 ` Lukas Hejtmanek
2011-07-22 6:56 ` Kiyoshi Ueda
2011-07-22 8:19 ` Lukas Hejtmanek
2011-07-23 7:28 ` Jun'ichi Nomura
2011-07-24 22:16 ` Lukas Hejtmanek
2011-08-01 9:31 ` Kiyoshi Ueda
2011-09-08 13:27 ` Lukas Hejtmanek [this message]
2011-09-15 18:49 ` Mike Snitzer
2011-09-16 14:08 ` Lukas Hejtmanek
2011-09-19 5:50 ` Jun'ichi Nomura
2011-09-29 20:57 ` Lukas Hejtmanek
2011-10-05 8:13 ` Jun'ichi Nomura
2011-10-05 10:35 ` Lukas Hejtmanek
2011-10-06 5:11 ` Jun'ichi Nomura
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=20110908132756.GT31717@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=agk@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=k-ueda@ct.jp.nec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome