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: <20080918164535.5e9f77a8@hskinnemo-gx745.norway.atmel.com>
Date:	Thu, 18 Sep 2008 16:45:35 +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:
> 
> > Wouldn't it be better if the dmaengine layer made sure it didn't pass
> > the same channel several times to a client?  
> 
> Wouldn't that require it to keep track of which clients have already seen which
> channels?  It might make more sense, but it's probably easier the current way.

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

How common is for several clients to use the same channel anyway
though? Wouldn't you risk stalling the network stack if the md subsystem
has submitted a large xor operation on the same channel that the
network stack was about to use?

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/