[Bugs] [Bug 1693575] New: gfapi: do not block epoll thread for upcall notifications

bugzilla at redhat.com bugzilla at redhat.com
Thu Mar 28 08:49:01 UTC 2019


            Bug ID: 1693575
           Summary: gfapi: do not block epoll thread for upcall
           Product: GlusterFS
           Version: mainline
          Hardware: All
                OS: All
            Status: NEW
         Component: libgfapi
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: skoduri at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Description of problem:

With https://review.gluster.org/#/c/glusterfs/+/21783/, we have made changes to
offload processing upcall notifications to synctask so as not to block epoll
threads. However seems like the purpose wasnt fully resolved. 

In "glfs_cbk_upcall_data" -> "synctask_new1" after creating synctask if there
is no callback defined, the thread waits on synctask_join till the syncfn is
finished. So that way even with those changes, epoll threads are blocked till
the upcalls are processed.

Hence the right fix now is to define a callback function for that synctask
"glfs_cbk_upcall_syncop" so as to unblock epoll/notify threads completely and
the upcall processing can happen in parallel by synctask threads.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

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

More information about the Bugs mailing list