linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>, Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)
Date: Fri, 28 Dec 2007 15:37:28 -0600	[thread overview]
Message-ID: <47756C98.3080804@shaw.ca> (raw)
In-Reply-To: <4755FA35.5000105@shaw.ca>

Robert Hancock wrote:
> Jeff Garzik wrote:
>> Robert Hancock wrote:
>>> This fixes some problems with ATAPI devices on nForce4 controllers in 
>>> ADMA mode
>>> on systems with memory located above 4GB. We need to delay setting 
>>> the 64-bit
>>> DMA mask until the PRD table and padding buffer are allocated so that 
>>> they don't
>>> get allocated above 4GB and break legacy mode (which is needed for ATAPI
>>> devices).
>>>
>>> Signed-off-by: Robert Hancock <hancockr@shaw.ca>
>>
>> This is a bit nasty :/
>>
>> I would consider setting the consistent DMA mask to 32-bit, and 
>> setting the overall mask to 64-bit.
>>
>> Seems like that would solve the problem?
> 
> The issue with that is that it would also constrain the ADMA CPB/PRD 
> table allocation to 32-bit, which I'd rather avoid having to do. There 
> are dual-socket Opteron boxes like HP xw9300 that use this controller, 
> and limiting the allocation to 32-bit could force a non-optimal node 
> allocation for the table memory.
> 
> These type of devices really want a version of dma_alloc_coherent that 
> allows overriding the DMA mask for specific allocations to make this 
> cleaner. I'm sure this isn't the only device that has different DMA mask 
> requirements for different consistent memory allocations..
> 
> This patch does has the advantage of being confirmed to fix the 
> reporter's problem (https://bugzilla.redhat.com/show_bug.cgi?id=351451) 
> which there's something to be said for this late in the .24-rc series..
> 
>>
>> Also, does this need to be rebased on top of what I just pushed upstream?
> 
> It don't think so.. this change is independent from the "sata_nv: don't 
> use legacy DMA in ADMA mode (v3)" patch you just merged.

This bug fix is still outstanding. I haven't heard any more comments on 
this one recently..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


  reply	other threads:[~2007-12-28 21:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  2:04 [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3) Robert Hancock
2007-11-23 15:22 ` Mark Lord
2007-11-23 17:30   ` Morrison, Tom
2007-11-23 17:46     ` Mark Lord
2007-11-23 18:47       ` Morrison, Tom
2007-11-23 20:40         ` Mark Lord
2007-11-24  0:13       ` Robert Hancock
2007-11-24  0:20         ` Jeff Garzik
2007-11-24  0:31           ` Robert Hancock
2007-11-24  2:48           ` Mark Lord
2007-11-24  5:12 ` Tejun Heo
2007-12-04 22:17 ` Jeff Garzik
2007-12-05  1:09   ` Robert Hancock
2007-12-28 21:37     ` Robert Hancock [this message]
2007-12-08 18:36   ` Robert Hancock
2007-12-17 11:44 ` shyam_iyer
2007-12-17 16:17   ` shyam_iyer
2007-12-18  2:50     ` Tejun Heo
2007-12-18  3:52     ` Tejun Heo
2007-12-18 10:22       ` Shyam_Iyer
2007-12-18 12:12         ` Shyam_Iyer
2007-12-20 11:15           ` shyam_iyer
2007-12-17 11:47 ` shyam_iyer

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=47756C98.3080804@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).