[Bugs] [Bug 1220041] timer wheel and throttling in bitrot

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1220041



--- Comment #28 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10716 committed in release-3.7 by Niels de
Vos (ndevos at redhat.com) 
------
commit 1a217b2a0295ca4d9068ee5c17d6a4374cc5f8fc
Author: Venky Shankar <vshankar at redhat.com>
Date:   Fri Apr 24 10:10:35 2015 +0530

    core: Global timer-wheel

    Instantiate a process wide global instance of the timer wheel
    data structure. Spawning glusterfs* process with option arg
    "--global-timer-wheel" instantiates a global instance of
    timer-wheel under global context (->ctx).

    Translators can make use of this process wide instance [via a
    call to glusterfs_global_timer_wheel()] instead of maintaining
    an instance of their own and possibly consuming more memory.
    Linux kernel too has a single instance of timer wheel where
    subsystems such as IO, networking, etc.. make use of.

    Bitrot daemon would be early consumers of this: bitrot translator
    instances for multiple volumes would track objects belonging to
    their respective bricks in this global expiry tracking data
    structure. This is also a first step to move GlusterFS timer
    mechanism to use timer-wheel.

    > Change-Id: Ie882df607e07acaced846ea269ebf1ece306d6ae
    > BUG: 1170075
    > Signed-off-by: Venky Shankar <vshankar at redhat.com>
    > Reviewed-on: http://review.gluster.org/10380
    > Tested-by: NetBSD Build System
    > Reviewed-by: Vijay Bellur <vbellur at redhat.com>
    > Tested-by: Gluster Build System <jenkins at build.gluster.com>

    Change-Id: I35c840daa9996a059699f8ea5af54c76ede7e09c
    Signed-off-by: Venky Shankar <vshankar at redhat.com>
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    BUG: 1220041
    Reviewed-on: http://review.gluster.org/10716
    Tested-by: Gluster Build System <jenkins at build.gluster.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.