lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <4534185C.9060401@shaw.ca>
Date:	Mon, 16 Oct 2006 17:40:12 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Mark Lord <liml@....ca>
Cc:	Jens Axboe <jens.axboe@...cle.com>,
	Allen Martin <AMartin@...dia.com>,
	Jeff Garzik <jeff@...zik.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, prakash@...noor.de
Subject: Re: [RFC PATCH] nForce4 ADMA with NCQ: It's aliiiive..

Mark Lord wrote:
> Robert Hancock wrote:
>>
>> I also noticed that I'm still using the default 64KB libata 
>> dma_boundary value, this should be 4GB for ADMA mode (but fixed up 
>> back to the default if an ATAPI device is connected, same as with the 
>> DMA mask).
> 
> Be careful of that.  The original PDC hardware for ADMA still had
> the "don't cross a 64KB boundary" requirement.
> 
> Cheers

That is part of the ADMA spec - but in that case, how come the 
pdc_adma.c driver sets the dma_boundary in the SCSI host template to 
4GB? That seems wrong.

In any case, however, I really doubt the NVIDIA ADMA controller shares 
this limitation - they provide 32 bits for the region length (standard 
ADMA only has 16 bits), which wouldn't be very useful if you couldn't 
cross a 64KB boundary..

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ