From: Jens Axboe <axboe@suse.de>
To: erich <erich@areca.com.tw>
Cc: 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,
James Bottomley <James.Bottomley@steeleye.com>,
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 11:39:10 +0200 [thread overview]
Message-ID: <20060420093909.GA13279@suse.de> (raw)
In-Reply-To: <001101c6645d$5c3e9820$b100a8c0@erich2003>
Erich, please stop top posting! I've asked you several times now.
On Thu, Apr 20 2006, erich wrote:
> Dear Dear Jens Axboe,
>
> I will try debench on the fs with larger xfer size when I enter my Lab.
> next time.
> In the previous testing I do iometer and bonnie++ bench with ext3 riserfs
> file system.
> I have test the transfer size from 2K to 5M with random/sequence read/write
> each term 2 hours.
> When those three testing platforms all have completion.
> There were not any one message appear as this.
> I have done same testing with ext2 512 sectors and all done well.
> I will find the difference of each LBA value , request length between 512
> sectors and 4096 sectors.
Since you are a hardware vendor, you probably have access to various
hardware analyzers that you can hook up. It seems to be easily
reproducible for you with ext2, why don't you see if you bus traffic
corresponds to what you expect with 4096 xfer size?
Again, I don't think I can help you with this. We have larger
max_sectors drivers out there and experience no problems. I'm fairly
confident that this is a bug in your driver/hardware that you need to
work out.
--
Jens Axboe
next prev parent reply other threads:[~2006-04-20 9:38 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 ` new Areca driver in 2.6.16-rc6-mm2 appears to be broken 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 [this message]
2006-04-20 12:53 ` James Bottomley
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=20060420093909.GA13279@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--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