linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tirumalareddy marri <tirumalareddymarri@yahoo.com>
To: thomas62186218@aol.com, linux-raid@vger.kernel.org
Subject: Re: Debugging new HW  XOR engine driver
Date: Tue, 15 Jul 2008 09:59:43 -0700 (PDT)	[thread overview]
Message-ID: <817998.29129.qm@web81306.mail.mud.yahoo.com> (raw)

I am working AMCC powerPC based SoC. It has XOR engine built in the HW.  
Thanks,
Marri

----- Original Message ----
From: "thomas62186218@aol.com" <thomas62186218@aol.com>
To: tirumalareddymarri@yahoo.com; linux-raid@vger.kernel.org
Sent: Tuesday, July 15, 2008 9:35:15 AM
Subject: Re: Debugging new HW XOR engine driver

Regarding your HW XOR driver, is this for Intel x86 or some other 
platform. I am assuming x86 since you did not mention another other 
processor platform but in that case, what hardware are you using for 
XOR?

-Thomas


-----Original Message-----
From: tirumalareddy marri <tirumalareddymarri@yahoo.com>
To: linux-raid@vger.kernel.org
Sent: Mon, 14 Jul 2008 11:26 am
Subject: Debugging new HW  XOR engine driver










I am new to this mailing list. I am working on adding driver for HW 
accelerated
XOR engine. I am able to get XOR engine working and created ADMA 
interface . I
am able to create RAID-5 using mdadm. After creating filesystem, I 
tried to
mount the /dev/md0 . It failied to mount saying that 
"ext3_check_descriptors:
Block bitmap for group 384 not in group" . For sure there is some thing 
wrong at
driver level.
  I used "dd" command to read/write to /dev/md0. It seems read/writes 
are not a
problem. When I do small file sizes of 10K , everything fine. When I 
write a
file of size of 1MB or above seems to have issue. Looks like partial 
write fine
too.
  I am looking for the ways to debug the problem. Also looking for 
suggestions
from the people who developed HW accelerated drivers and the issue thy 
run into.
Are the some tools to identify the corruptions.
Thanks in Advance.
--Tirumala

--
To unsubscribe from this list: send=2
0the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html





--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-07-15 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 16:59 tirumalareddy marri [this message]
2008-07-15 18:34 ` Debugging new HW XOR engine driver Dan Williams
  -- strict thread matches above, loose matches on Subject: below --
2008-07-18  6:55 tirumalareddy marri
2008-07-18  1:37 tirumalareddy marri
2008-07-15 22:52 tirumalareddy marri
2008-07-16  6:48 ` Dan Williams
2008-07-15 20:19 tirumalareddy marri
2008-07-14 18:26 tirumalareddy marri
2008-07-15 16:35 ` thomas62186218

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=817998.29129.qm@web81306.mail.mud.yahoo.com \
    --to=tirumalareddymarri@yahoo.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas62186218@aol.com \
    /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).