linux-kernel - Re: dmaengine.c: question about device_alloc_chan

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: <20080918170058.70b562c9@hskinnemo-gx745.norway.atmel.com>
Date:	Thu, 18 Sep 2008 17:00:58 +0200
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	Timur Tabi <timur@...escale.com>
Cc:	Dan Williams <dan.j.williams@...el.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: dmaengine.c: question about device_alloc_chan_resources

Timur Tabi <timur@...escale.com> wrote:
> Haavard Skinnemoen wrote:
> 
> > I guess so. What would be even more simple is to simply prevent other
> > clients from taking a channel once someone has acked it, which would be
> > perfect for my purposes, but perhaps not everyone else's...  
> 
> I'm not clear on how your driver works, but doesn't it run continuous tests on
> all channels all the time?  If so, wouldn't your proposal prevent other drivers
> from ever getting a DMA channel?

You can explicitly tell it which channel(s) to use. If you run it on
all channels, it will already prevent any dmaslave clients from ever
getting a channel.

dmatest is meant for testing only, and has a major impact on system
performance when it's running, so it's IMO not a very interesting use
case.

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