linux-kernel - Re: Driver for tightly coupled memory

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: <24229.1221619342@turing-police.cc.vt.edu>
Date:	Tue, 16 Sep 2008 22:42:22 -0400
From:	Valdis.Kletnieks@...edu
To:	Alessio Sangalli <alesan@...oweb.com>
Cc:	Ben Nizette <bn@...sdigital.com>, Ben Dooks <ben-linux@...ff.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Driver for tightly coupled memory

On Tue, 16 Sep 2008 15:49:53 PDT, Alessio Sangalli said:

> In this case however, do you imply that a device driver will just do all
> the genalloc stuff? In this case it has to know about the TCM details,

What sort of hardware/software interface does the TCM provide?  You mentioned
that it could be accessed even while main memory is being accessed - what does
that look like from the software level?

Content of type "application/pgp-signature" skipped