On Mon, Jan 25, 2016 at 01:08:38PM +0530, Ravishankar N wrote: > On 01/25/2016 12:56 PM, Venky Shankar wrote: > >Also, it would be beneficial to have the core TBF implementation as part of > >libglusterfs so as to be consumable by the server side xlator component to > >throttle dispatched FOPs and for daemons to throttle anything that's outside > >"brick" boundary (such as cpu, etc..). > That makes sense. We were initially thinking to overload posix_rchecksum() > to do the SHA256 sums for the signer. That does have advantages by avoiding network rountrips by computing SHA* locally. TBF could still implement ->rchecksum and throttle that (on behalf of clients, residing on the server - internal daemons). Placing the core implementation as part of libglusterfs would still provide the flexibility. > > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
