From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jens Axboe <axboe@suse.de>
Cc: erich <erich@areca.com.tw>,
dax@gurulabs.com, billion.wu@areca.com.tw,
Al Viro <viro@ftp.linux.org.uk>, Andrew Morton <akpm@osdl.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Matti Aarnio <matti.aarnio@zmailer.org>,
linux-kernel@vger.kernel.org, Chris Caputo <ccaputo@alt.net>
Subject: Re: new Areca driver in 2.6.16-rc6-mm2 appears to be broken
Date: Thu, 20 Apr 2006 08:53:37 -0400 [thread overview]
Message-ID: <1145537618.3446.5.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060420082357.GU614@suse.de>
On Thu, 2006-04-20 at 10:23 +0200, Jens Axboe wrote:
> It was just a suggestion, the bug might very well be just the size of
> the transfer itself and nothing SG related. All I can say for sure is
> that I'd be very surprised if this fs corruption isn't due to the
> hardware mangling the data for large transfers.
It sounds like this to me as well. The other problem might be some type
of segment boundary issue which are not uncommon on less capable DMA
engines. Either way, there's no question that large transfers work on
other hardware (SGI and IBM have extensively tested raising the current
128SG entries limit just so they could squeeze megabytes of data per
single command), so as Jens says, this is some type of issue within the
Areca hardware which you need to understand before the driver can be
made safe.
James
next prev parent reply other threads:[~2006-04-20 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0603212310070.20655@nacho.alt.net>
2006-03-30 8:54 ` erich
2006-03-30 15:46 ` Chris Caputo
[not found] ` <004a01c65470$412daaa0$b100a8c0@erich2003>
[not found] ` <20060330192057.4bd8c568.akpm@osdl.org>
[not found] ` <20060331074237.GH14022@suse.de>
2006-03-31 8:36 ` erich
2006-04-12 13:20 ` erich
2006-04-19 10:40 ` Jens Axboe
2006-04-19 13:16 ` erich
2006-04-19 13:19 ` Jens Axboe
2006-04-20 1:54 ` erich
2006-04-20 6:42 ` Jens Axboe
2006-04-20 8:11 ` erich
2006-04-20 8:23 ` Jens Axboe
2006-04-20 9:32 ` erich
2006-04-20 9:39 ` Jens Axboe
2006-04-20 12:53 ` James Bottomley [this message]
2006-04-20 15:38 ` Randy.Dunlap
2006-04-25 8:45 ` erich
2006-04-25 16:02 ` Randy.Dunlap
2006-04-26 3:24 ` erich
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=1145537618.3446.5.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=billion.wu@areca.com.tw \
--cc=ccaputo@alt.net \
--cc=dax@gurulabs.com \
--cc=erich@areca.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=rdunlap@xenotime.net \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®