[lkml]   [2006]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: feature-removal-schedule obsoletes
    On Tue, Oct 31, 2006 at 04:57:56PM +0100, J?rn Engel wrote:
    > 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?

    As I understand it, there is no guarantee that a block drivers request
    function will be called in process context - it could be called in
    interrupt context.

    The MMC subsystem needs process context to issue commands since the
    process of issuing commands entails various sleeps. Hence why the
    MMC block has its own process context.

    Russell King
    Linux kernel 2.6 ARM Linux -
    maintainer of: 2.6 Serial core
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-10-31 20:35    [W:0.020 / U:12.084 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site