Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-30 Thread Ming Lei
On Fri, May 1, 2015 at 12:59 AM, Jeff Moyer wrote: > Ming Lei writes: > >> On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer wrote: >>> Ming Lei writes: >>> If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-30 Thread Jeff Moyer
Ming Lei writes: > On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer wrote: >> Ming Lei writes: >> >>> If there are too many pending per work I/O, too many >>> high priority work thread can be generated so that >>> system performance can be effected. >>> >>> This patch limits the max pending per

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-30 Thread Jeff Moyer
Ming Lei ming@canonical.com writes: On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer jmo...@redhat.com wrote: Ming Lei ming@canonical.com writes: If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can be effected.

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-30 Thread Ming Lei
On Fri, May 1, 2015 at 12:59 AM, Jeff Moyer jmo...@redhat.com wrote: Ming Lei ming@canonical.com writes: On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer jmo...@redhat.com wrote: Ming Lei ming@canonical.com writes: If there are too many pending per work I/O, too many high priority work

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Ming Lei
On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer wrote: > Ming Lei writes: > >> If there are too many pending per work I/O, too many >> high priority work thread can be generated so that >> system performance can be effected. >> >> This patch limits the max pending per work I/O as 16, >> and will

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Jeff Moyer
Ming Lei writes: > If there are too many pending per work I/O, too many > high priority work thread can be generated so that > system performance can be effected. > > This patch limits the max pending per work I/O as 16, > and will fackback to single queue mode when the max > number is reached.

[PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Ming Lei
If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can be effected. This patch limits the max pending per work I/O as 16, and will fackback to single queue mode when the max number is reached. This patch fixes Fedora 22 live

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Ming Lei
On Wed, Apr 29, 2015 at 12:36 AM, Jeff Moyer jmo...@redhat.com wrote: Ming Lei ming@canonical.com writes: If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can be effected. This patch limits the max pending per

Re: [PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Jeff Moyer
Ming Lei ming@canonical.com writes: If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can be effected. This patch limits the max pending per work I/O as 16, and will fackback to single queue mode when the max

[PATCH] block: loop: avoiding too many pending per work I/O

2015-04-28 Thread Ming Lei
If there are too many pending per work I/O, too many high priority work thread can be generated so that system performance can be effected. This patch limits the max pending per work I/O as 16, and will fackback to single queue mode when the max number is reached. This patch fixes Fedora 22 live