linux-kernel - Re: [PATCH 07/31] blk-throttle: removed deferred config application mechanism

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 May 2013 10:27:58 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	axboe@...nel.dk, linux-kernel@...r.kernel.org, lizefan@...wei.com,
	containers@...ts.linux-foundation.org, cgroups@...r.kernel.org
Subject: Re: [PATCH 07/31] blk-throttle: removed deferred config application
 mechanism

On Thu, May 02, 2013 at 10:49:12AM -0400, Vivek Goyal wrote:
> > +	/* kick dispatch in case disptime got shortened */
> >  	throtl_schedule_delayed_work(td, 0);
> 
> Hi Tejun,
> 
> Do we need above throtl_schedule_delayed_work() now?
> throtl_schedule_next_dispatch() should take care of it. And if group
> is not on service tree at the time of limit change, then anyway, we don't
> have to schedule any work.

Right, that one can go away.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/