[lkml]   [2002]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ANNOUNCE] EVMS Release 1.2.0
    On Tuesday 01 October 2002 05:20, Jens Axboe wrote:
    > On Mon, Sep 30 2002, Kevin Corry wrote:
    > > The EVMS team is announcing the next stable release of the Enterprise
    > > Volume Management System, which will eventually become EVMS 2.0. Package
    > > 1.2.0 is now available for download at the project web site:
    > >
    > [evms.c]
    > #ifndef CONFIG_SMP
    > static spinlock_t evms_request_lock = SPIN_LOCK_UNLOCKED;
    > #endif
    > ...
    > #ifdef CONFIG_SMP
    > blk_dev[EVMS_MAJOR].queue = evms_find_queue;
    > #else
    > blk_init_queue(BLK_DEFAULT_QUEUE(EVMS_MAJOR),
    > evms_do_request_fn, &evms_request_lock);
    > blk_queue_make_request(BLK_DEFAULT_QUEUE(EVMS_MAJOR),
    > evms_make_request_fn);
    > #endif
    > ...
    > #ifdef CONFIG_SMP
    > lv->request_lock = SPIN_LOCK_UNLOCKED;
    > blk_init_queue(&lv->request_queue,
    > evms_do_request_fn,
    > &lv->request_lock);
    > blk_queue_make_request(&lv->request_queue,
    > evms_make_request_fn);
    > #endif
    > What the hell is that about?

    The above code implements a single request queue for the EVMS driver on
    uniprocessor, and per-volume request queues on SMP. This was done quite some
    time ago (before 2.5), since we felt SMP was the only place where there was a
    performance advantage to having multiple queues (and thus using up all the
    extra memory on UP was wasteful). Since a lot of things have changed in 2.5
    (e.g. prempt), there might be performance advantages on UP now as well.

    I was reading over the kernel Bitkeeper changelogs last night and noticed you
    made some changes to the loop driver to implement per-device queues. I talked
    this over with Mark and we decided that if this was the trend, we would
    switch to always using per-volume queues. If you take a look at our bitkeeper
    tree, you should see that change is already in. Unfortunately, this was after
    1.2.0 was released, so that change isn't available in the package I announced
    yesterday. But, the 2.5 code changes almost daily anyway, so I'm not too
    worried. And from looking over the Bitkeeper logs, it looks like there are
    more gendisk changes in 2.5.40 that may affect EVMS, so there will probably
    be additional changes today.

    If you have any additional comments, please let us know.

    Kevin Corry
    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: 2005-03-22 13:29    [W:0.023 / U:6.148 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site