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: <48D03811.9070805@manoweb.com>
Date:	Tue, 16 Sep 2008 15:49:53 -0700
From:	Alessio Sangalli <alesan@...oweb.com>
To:	Ben Nizette <bn@...sdigital.com>
CC:	Ben Dooks <ben-linux@...ff.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Driver for tightly coupled memory

Ben Nizette wrote:

> If a driver needs a quick FIFO it can attempt to get the RAM for said
> FIFO from the genalloc and fall back to main memory otherwise.  Simple,
> flexible, easy :-)

Well, interesting, that is why I asked here before writing code.

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,
and problems may arise if more than one driver wants to use this
feature. Or, are you suggesting to write a small TCM driver that will do
the gen_pool_create() and gen_pool_add() and then export the struct
gen_pool for use by other drivers that may require it?

I mentioned implementing a FIFO because I already have a couple of
examples where this FIFO thing would be used.

Bye bye, thank you
Alessio

--
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/