----- Original Message ----- > From: "Emmanuel Dreyfus" <[email protected]> > To: "Raghavendra Gowdappa" <[email protected]>, "Pranith Kumar Karampuri" > <[email protected]> > Cc: [email protected] > Sent: Wednesday, September 2, 2015 8:12:37 PM > Subject: Re: [Gluster-devel] FOP ratelimit? > > Raghavendra Gowdappa <[email protected]> wrote: > > > Its helpful if you can give some pointers on what parameters (like > > latency, throughput etc) you want us to consider for QoS. > > Full blown QoS would be nice, but a first line of defense against > resource hogs seems just badly required. > > A bare minimum could be to process client's FOP in a round robin > fashion. That way even if one client sends a lot of FOPs, there is > always some window for others to slip in. > > Any opinion?
As of now we depend on epoll/poll events informing servers about incoming messages. All sockets are put in the same event-pool represented by a single poll-control fd. So, the order of our processing of msgs from various clients really depends on how epoll/poll picks events across multiple sockets. Do poll/epoll have any sort of scheduling? or is it random? Any pointers on this are appreciated. > > -- > Emmanuel Dreyfus > http://hcpnet.free.fr/pubz > [email protected] > _______________________________________________ Gluster-devel mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-devel
