Answers inline. Regards, Poornima
----- Original Message ----- > From: "Raghavendra Gowdappa" <rgowd...@redhat.com> > To: "Poornima Gurusiddaiah" <pguru...@redhat.com> > Cc: "Gluster Devel" <gluster-devel@gluster.org> > Sent: Wednesday, December 9, 2015 9:00:55 PM > Subject: libgfapi compound operations - multiple writes > > forking off since it muddles the original conversation. I've some questions: > > 1. Why do multiple writes need to be compounded together? If the application splits the large write into fixed sized chunks (Samba 64KB), it would be an option to compound it. > 2. If the reason is aggregation, cant we tune write-behind to do the same? Yes surely. IO-cache would be a better candidate? write behind mostly doesn't aggregate. Since this can also be one by compound fops, just added as good to have. But not mandatory as it can be achieved otherwise. > > regards, > Raghavendra. > _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
