[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMM=eLd9fToJ5Kh+vf4WG1ZN-qTc2CX98-+BUkFWWQQ=tCG7LQ@mail.gmail.com>
Date: Thu, 15 Sep 2011 14:49:52 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: Lukas Hejtmanek <xhejtman@....muni.cz>
Cc: Kiyoshi Ueda <k-ueda@...jp.nec.com>,
"Jun'ichi Nomura" <j-nomura@...jp.nec.com>, agk@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: request baset device mapper in Linux
2011/9/8 Lukas Hejtmanek <xhejtman@....muni.cz>:
> 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.
Does "with your patch" mean against 3.0.3 or the original 2.6.32 kernel?
If you apply the patch to the 3.0.3 kernel do you regain the performance?
Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists