linux-kernel - Re: feature-removal-schedule obsoletes

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]

Date:	Tue, 31 Oct 2006 16:57:56 +0100
From:	Jörn Engel <joern@...nheim.fh-wedel.de>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Arnd Bergmann <arnd@...db.de>, Christoph Hellwig <hch@....de>,
	Jiri Slaby <jirislaby@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Dominik Brodowski <linux@...do.de>,
	Harald Welte <laforge@...filter.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: feature-removal-schedule obsoletes

On Sat, 28 October 2006 10:34:51 +0200, Pierre Ossman wrote:
> 
> What should be used to replace it? The MMC block driver uses it to
> manage the block device queue. I am not that intimate with the block
> layer so I do not know the proper fix.

Why does the MMC block driver use a thread?  Is there a technical
reason for this or could it be done in original process context as
well, removing some code and useless cpu scheduler overhead?

Jörn

-- 
When people work hard for you for a pat on the back, you've got
to give them that pat.
-- Robert Heinlein
-
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/