Re: ionice: requires scheduling since 7ab08ba3e5e6f161b93ff2b3b7d5b18dc7b44510

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 22, 2011 at 12:21:08PM +0200, Voelker, Bernhard wrote:
> Karel Zak wrote:
> 
> > Fixed.
> > 
> >  I've also added support for human readable class names, you can use:
> > 
> >    ionice -c best-effort /bin/foo
> 
> great, thanks!
> 
> One last corner case regarding -t (ignoring failure):
> 
>   $ schedutils/ionice -c 4 -t  schedutils/ionice 
>   ionice: bad prio class 4
>   $ schedutils/ionice -n 8 -t  schedutils/ionice 
>   idle
> 
> With -c, a bad prio class leads to a failure, while it doesn't with -n.
> Is this intended?

OK. Copy & past from the latest commit:

    ionice: make -t more tolerant
    
    * replace errx() with warnx() for unknown -c class
    
      The right place to check I/O scheduler features is in kernel. We should
      not try to be more smart than kernel.
    
    * make the code ready (robust) for unknown sched.classes
    
    * fix -t behavior
    
    	old version:
    	  $ ionice -c 4 -t bash
    	  ionice: bad prio class 4
    
    	new version:
    	  $ ionice -c 4 -t bash
    
    Reported-by: Voelker, Bernhard" <bernhard.voelker@xxxxxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Karel Zak <kzak@xxxxxxxxxx>

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
 http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux