From: Tejun Heo <tj@kernel.org>
To: Mark Nelson <mdnelson8@gmail.com>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] ahci: Enable SB600 64bit DMA on MSI K9A2 Platinum
Date: Wed, 28 Oct 2009 13:14:33 +0100 [thread overview]
Message-ID: <4AE835A9.40806@kernel.org> (raw)
In-Reply-To: <65a6ef750910280449k5597d3abkc0995080954e5760@mail.gmail.com>
Mark Nelson wrote:
> Things look promising so far with lots of DMAs above 4GB (snippets
> from syslog):
It's probably working okay but a good test would be to repeat to copy
a large file and checksum it and verify checksums actually match.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-10-28 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 5:03 [PATCH] ahci: Enable SB600 64bit DMA on MSI K9A2 Platinum Mark Nelson
2009-10-26 13:25 ` Tejun Heo
[not found] ` <65a6ef750910261605q45a08791h53cc2afd5d006bb3@mail.gmail.com>
[not found] ` <4AE7382F.20302@kernel.org>
2009-10-27 22:51 ` Mark Nelson
2009-10-28 11:49 ` Mark Nelson
2009-10-28 12:14 ` Tejun Heo [this message]
2009-10-28 22:30 ` Mark Nelson
2009-10-29 8:32 ` Mark Nelson
2009-11-03 8:57 ` Mark Nelson
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=4AE835A9.40806@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mdnelson8@gmail.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).