gluster/glusterfs
1
0
Fork 0
mirror of https://github.com/gluster/glusterfs.git synced 2026-02-06 09:48:44 +01:00
Code Issues Releases Wiki Activity
Files
master
glusterfs/doc/developer-guide/adding-fops.md
Humble Devassy Chirammal 8907f67ba2 doc: restructure developer docs to new layout 
The developer oriented information is scattered in source
and its very difficult to identify which are those.
With this patch subdirs are created under developer-guide
which will be the parent for developer notes. The changes
suggested in http://review.gluster.org/#/c/8827/ are also
included in this patch.

Change-Id: I4c8510d52c49f4066225f72cac8f97f087d6c70c
BUG: 1206539
Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
Reviewed-on: http://review.gluster.org/10038
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
2015-03-30 05:51:12 -07:00

733 B
Raw Permalink Blame History

Adding a new FOP

Steps to be followed when adding a new FOP to GlusterFS:

  1. Edit glusterfs.h and add a GF_FOP_* constant.
  2. Edit xlator.[ch] and:
    • add the new prototype for fop and callback.
    • edit xlator_fops structure.
  3. Edit xlator.c and add to fill_defaults.
  4. Edit protocol.h and add struct necessary for the new FOP.
  5. Edit defaults.[ch] and provide default implementation.
  6. Edit call-stub.[ch] and provide stub implementation.
  7. Edit common-utils.c and add to gf_global_variable_init().
  8. Edit client-protocol and add your FOP.
  9. Edit server-protocol and add your FOP.
  10. Implement your FOP in any translator for which the default implementation is not sufficient.
View Git Blame Copy Permalink