linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	NeilBrown <neilb@suse.de>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: Regression with calibrate_xor_blocks, probably UML related
Date: Fri, 11 Feb 2011 15:06:29 +0200	[thread overview]
Message-ID: <4D553455.6000409@panasas.com> (raw)
In-Reply-To: <AANLkTine1w2h29OPES1RHTs-otB_ohhMDMbbRoXFK+BB@mail.gmail.com>

On 02/11/2011 02:38 PM, richard -rw- weinberger wrote:
> On Thu, Feb 10, 2011 at 4:51 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
>> On 02/09/2011 09:02 PM, Boaz Harrosh wrote:
>>> I have a new module that uses the async_tx.h lib.
>>>
>>> On an exact same module code based on 3.6.37 I see the:
>>>       xor: measuring software checksum speed
>>>          8regs     : 11312.000 MB/sec
>>>          8regs_prefetch:  9792.800 MB/sec
>>>          32regs    : 11220.400 MB/sec
>>>          32regs_prefetch:  9750.800 MB/sec
>>>       xor: using function: 8regs (11312.000 MB/sec)
>>>
>>> And all is well. But on code based on 2.6.38-rc4 I get hard stuck
>>> right after:
>>>       xor: measuring software checksum speed
>>>
>>
>> OK this is not dependent on Kernel version it is the same for both
>> .38-rc4 and .37. I was just lucky with .37 more.
>>

Thanks richard.

I'm afraid it is not a regression. Just that I got lucky more
with 2.6.37. But it happens with 2.6.37 just the same.

>> And the same things happen with raid456 module. I do
>> []$ modprobe raid456; modprobe --remove raid456
>> A few times it loads, printing the above checks, Then At one
>> time it freezes. Sometimes at first attempt sometimes at 4-7
>> attempts. I never went 10 times strait.
>>
>> When it freezes (hard) I can see in my host that the UML is
>> at 100% CPU.
>>
>> BTW: when I manage to pass the tests I get the above numbers
>> But when I load directly on the host I get:
>>
<>
>> Any way I'm trying to debug that xor.ko loading problem see what
>> comes up. Any help is welcome
> 
> Hmmm, can you bisect it?
> Can you post you config then I can also try my best...
> 

You mean that you can setup a UML and try it out for yourself?
All I did was:
[]$ make ARCH=um defconfig
Then turn on raid456 in "make ARCH=um xconfig"

when you load into the UML just, "modprobe raid456

Thanks
Boaz

>> Thanks
>> Boaz
>>
>>> the UML is completely frozen. When I kill the uml from the host
>>> I can sometimes get this trace.

      reply	other threads:[~2011-02-11 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 19:02 Regression with calibrate_xor_blocks, probably UML related Boaz Harrosh
2011-02-10 15:51 ` Boaz Harrosh
2011-02-11 12:38   ` richard -rw- weinberger
2011-02-11 13:06     ` Boaz Harrosh [this message]

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=4D553455.6000409@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=richard.weinberger@gmail.com \
    --cc=user-mode-linux-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).