From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Moore, Eric Dean'" <Eric.Moore@lsil.com>, linux-scsi@vger.kernel.org
Subject: RE: mpt fusion driver performance issue in 2.6.14-rc2
Date: Wed, 12 Oct 2005 14:05:09 -0700 [thread overview]
Message-ID: <200510122105.j9CL5Vg29053@unix-os.sc.intel.com> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C04746B82@nacos172.co.lsil.com>
Moore, Eric Dean wrote on Wednesday, October 12, 2005 1:58 PM
> There have been several post circulating about the "release failed"
> issue. I thought I saw an email recently from someone at Intel
> that had root caused the problem. I'm been trying to find that all day
> to find that email. I believe it was on this or the linux-kernel
> forums. Had you seen it?
Are you referring to this thread:
http://marc.theaimsgroup.com/?t=112802043200007&r=1&w=2
If it is, then it was me originally posted the patch.
> Anyways the plan is to eventually go to SPI transport. Have you seen
> this post by James?
> http://marc.theaimsgroup.com/?l=linux-scsi&m=112879629201766&w=2
>
> I have it on my todo list, and plan to review this SPI updates
> sometime this week. Perhaps you can try this patch out and let us
> (and James) whether its solved.
I suppose I can just run that patch through our benchmark setup.
- Ken
next prev parent reply other threads:[~2005-10-12 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 20:57 mpt fusion driver performance issue in 2.6.14-rc2 Moore, Eric Dean
2005-10-12 21:05 ` Chen, Kenneth W [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-14 0:07 Moore, Eric Dean
[not found] <B05667366EE6204181EABE9C1B1C0EB50484F7D4@scsmsx401.amr.corp.intel.com>
2005-10-01 0:27 ` Chen, Kenneth W
2005-10-01 6:19 ` Moore, Eric Moore
2005-10-12 1:10 ` Chen, Kenneth W
2005-09-29 18:59 Chen, Kenneth W
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=200510122105.j9CL5Vg29053@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=Eric.Moore@lsil.com \
--cc=linux-scsi@vger.kernel.org \
/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