Bug 762477 (GLUSTER-745) - better thread selector
Summary: better thread selector
Keywords:
Status: CLOSED DUPLICATE of bug 762315
Alias: GLUSTER-745
Product: GlusterFS
Classification: Community
Component: io-threads
Version: 3.0.3
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-21 03:04 UTC by Ian Rogers
Modified: 2010-03-23 11:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ian Rogers 2010-03-21 03:04:29 UTC 
xlators/performance/io-threads/src/io-threads.c contains the comment

        /* Decide which thread will service the request.
         * FIXME: This should change into some form of load-balancing.
         * */
        rand = random ();


Can this be scheduled to be done please? A simple round-robin - just incremement a counter - should be more likely to pick an available worker.
Comment 1 Amar Tumballi 2010-03-23 08:31:34 UTC 
> 
> 
> Can this be scheduled to be done please? A simple round-robin - just
> incremement a counter - should be more likely to pick an available worker.

This has been fixed as part of bug 762315 in mainline and would be available in 3.1 release.

*** This bug has been marked as a duplicate of bug 583 ***
Note You need to log in before you can comment on or make changes to this bug.