linux-kernel - Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090811084302.GB3251@braap.org>
Date:	Tue, 11 Aug 2009 10:43:02 +0200
From:	"Emilio G. Cota" <cota@...ap.org>
To:	Martyn Welch <martyn.welch@...anuc.com>
Cc:	Greg K-H <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

Martyn Welch wrote:
> Emilio G. Cota wrote:
>> Again, he (the driver writer) should know *nothing* about that.
>>
>> As for the scatter-gather case, what should happen is:
>>
>> User:		hey, there's a buffer I want to transfer. here's
>> 		a pointer and size
> Buffer where? On VME or PCI, where are you transferring it to? The API I  
> have will allow scattered locations on VME to be copied to PCI and  
> visa-versa, scattered locations on PCI to be copied to VME and  
> visa-versa. Even scattered locations on VME to scattered locations on  
> PCI with a bit of effort.

Admittedly our current tsi148 driver deals with the most common
situation: DMA from main (master) CPU RAM to/from a VME slave.

I'm not claiming we shouldn't support sg lists; however the
implementation should resemble the existing sg interfaces.
I'm currently working on something along those lines.

Thanks,
E.
--
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/