The patch titled
     Subject: umem: fix up unplugging
has been removed from the -mm tree.  Its filename was
     umem-fix-up-unplugging.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
From: Tao Guo <[email protected]>
Subject: umem: fix up unplugging

In 7eaceaccab5f40bbf ("block: remove per-queue plugging"), Jens removed
the whole mm_unplug_device() function, which used to be the trigger to
make umem start to work.

We need to implement unplugging to make umem start to work, or I/O will
never be triggered.

Signed-off-by: Tao Guo <[email protected]>
Cc: Neil Brown <[email protected]>
Cc: Jens Axboe <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---

 drivers/block/umem.c |   11 +++++++++++
 1 file changed, 11 insertions(+)

diff -puN drivers/block/umem.c~umem-fix-up-unplugging drivers/block/umem.c
--- a/drivers/block/umem.c~umem-fix-up-unplugging
+++ a/drivers/block/umem.c
@@ -513,6 +513,15 @@ static void process_page(unsigned long d
        }
 }
 
+static void mm_unplug(struct blk_plug_cb *cb)
+{
+       struct cardinfo *card = cb->q->queuedata;
+
+       spin_lock_irq(&card->lock);
+       activate(card);
+       spin_unlock_irq(&card->lock);
+}
+
 static void mm_make_request(struct request_queue *q, struct bio *bio)
 {
        struct cardinfo *card = q->queuedata;
@@ -523,6 +532,8 @@ static void mm_make_request(struct reque
        *card->biotail = bio;
        bio->bi_next = NULL;
        card->biotail = &bio->bi_next;
+       if (bio->bi_rw & REQ_SYNC || !blk_check_plugged(q, mm_unplug))
+               activate(card);
        spin_unlock_irq(&card->lock);
 
        return;
_

Patches currently in -mm which might be from [email protected] are

linux-next.patch

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to