reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jaroslav Fojtik <jafojtik@seznam.cz>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Question about reiser performance - short system freezes
Date: Thu, 24 Feb 2011 19:29:24 +0100	[thread overview]
Message-ID: <4D66A384.9000005@gmail.com> (raw)
In-Reply-To: <4D65CEAF.31101.5A677E@jafojtik.seznam.cz>

On 02/24/2011 04:21 AM, Jaroslav Fojtik wrote:
> Dear Edward Shishkin,
>
>>> May be that my comment might be userfull for your reiser development:
>>>
>>> I am facing following performance issue. The reiser works without data loss,
>>> but system sometimes hangs for 15s, mouse cursor is frozen and after this
>>> period it continues to work without any problem. It is strange, because I have 6 cores
>>> and all of them seems to be locked and waiting for something.
>>>
>>> Hanging occurs during intensive file search like find, or first phase
>>> of rsync.
>>>
>>> It seems to me that both reiser3 and reiser4 suffer by this issue.
>>> I have found BKL inside reiser3, but reiser4 seems to be without BKL.
>>>
>>> It is also strange that OS resides on different partition that should not
>>> be affected by reiser locking.
>>>
>>> May be that it could be problem large say 600GB HDD partition. But these partitins
>>> are normal nowadays.
>>>
>>> Is there any idea how to overcome this issue?
>>>
>>
>> Which kernel version?
>
> I have tested these kernels: 2.6.32.11 and 2.6.34.

Hello Jaroslav.

It might be a regression that have been fixed in the latest
kernels. Consider upgrading to .37. If it doesn't disappear,
then please send the SysRq-w output.

Thanks,
Edward.

  reply	other threads:[~2011-02-24 18:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  0:19 Question about reiser performance - short system freezes Jaroslav Fojtik
2011-02-24 12:07 ` Edward Shishkin
2011-02-24  3:21   ` Jaroslav Fojtik
2011-02-24 18:29     ` Edward Shishkin [this message]
2011-03-01 15:12       ` Re2: " Jaroslav Fojtik
2011-03-01 16:42         ` Edward Shishkin
2011-03-01 21:00           ` Re4: " Jaroslav Fojtik
2011-03-01 21:19             ` Nicolas Barbier
2011-03-01 21:23             ` Edward Shishkin
2011-03-01 21:24               ` Edward Shishkin
2011-03-03 21:26               ` Re6: " Jaroslav Fojtik
2011-03-03 22:09                 ` Edward Shishkin
2011-03-03 23:24                   ` Re8: Question about reiser performance - linux-2.6.37 crash reproduced Jaroslav Fojtik
2011-03-03 23:29                     ` Edward Shishkin
2011-03-03 23:38                       ` Re10: " Jaroslav Fojtik
2011-03-04 14:30                         ` Edward Shishkin
2011-04-16 11:17                         ` doiggl
     [not found]                       ` <4D7161F7.2754.6FF32@jafojtik.seznam.cz>
2011-03-04 22:58                         ` linux-2.6.37 crash reproduced - here is a screenshot Edward Shishkin
     [not found]                           ` <4D7214C2.30303.1B55FC@jafojtik.seznam.cz>
2011-03-05 22:44                             ` Re2: " Edward Shishkin
2011-03-09 22:16                             ` Edward Shishkin

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=4D66A384.9000005@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=jafojtik@seznam.cz \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).