[Bugs] [Bug 1467614] Gluster read/write performance improvements on NVMe backend

[bugzilla at redhat.com]

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



--- Comment #22 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17687 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit ecc5b30289be1a63e2616733a022b3a9a35f12b7
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Wed Jun 21 12:56:14 2017 +0530

    socket: Use granular mutex locks during pollin and pollout event processing

    ... instead of one global lock. This is because pollin and pollout
    processing code operate on mutually exclusive members of
    socket_private_t. Keeping this in mind, this patch introduces
    the more granular priv->in_lock and priv->out_lock locks.

    For pollerr, which modifies both priv->incoming and priv->ioq, both
    locks need to be taken.

    Change-Id: Id7aeb608dc7755551b6b404470d5d80709c81960
    BUG: 1467614
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-on: https://review.gluster.org/17687
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=F5a1MyZq7n&a=cc_unsubscribe