[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: busybox Digest, Vol 172, Issue 7
From:       Fryderyk Wrobel <frd1996 () gmail ! com>
Date:       2019-11-09 16:13:12
Message-ID: CAL25=yFkcvuPO3vzoR1zw1m8Rvj8UVLEWJa5dN0s8GC5VzxM4g () mail ! gmail ! com
[Download RAW message or body]

Hi,

This is described here:

https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

Kind regards,
Fryderyk

2019-11-09 12:00 GMT, busybox-request@busybox.net <busybox-request@busybox.net>:
> Send busybox mailing list submissions to
> 	busybox@busybox.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.busybox.net/mailman/listinfo/busybox
> or, via email, send a message with subject or body 'help' to
> 	busybox-request@busybox.net
>
> You can reach the person managing the list at
> 	busybox-owner@busybox.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of busybox digest..."
>
>
> Today's Topics:
>
>    1. Re: [git commit] taskset: add support for taking/printing CPU
>       list (-c option) (Xabier Oneca -- xOneca)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 9 Nov 2019 11:19:32 +0100
> From: Xabier Oneca  --  xOneca <xoneca@gmail.com>
> To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
> Cc: Busybox mailing list <busybox@busybox.net>
> Subject: Re: [git commit] taskset: add support for taking/printing CPU
> 	list (-c option)
> Message-ID:
> 	<CACkgH70A8XRP5Zn7XtbxvJmoWjDq4rT3S_w3OJd5YieNuHXrSQ@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Bernhard,
>
>> >+/*
>> >+ * Parse the CPU list and set the mask accordingly.
>> >+ *
>> >+ * The list element can be either a CPU index or a range of CPU
>> >indices.
>> >+ * Example: "1,3,5-7".
>> >+ *
>> >+ * note1: pattern specifiers after a range (e.g. 0-255:2/64) are not
>> >supported
>>
>> Why's that?
>>
>> Its late here and I'm probably too tired by now  but wouldn't just
>> recursing afterwards allow for that to work naturally?
>>
>> Thanks for beating it into vague sanity either way ;)
>> Cheers,
>
>  From taskset(1) (note: --cpu-list is same as -c):
>
>            --cpu-list 0-10:2
>                        is  processors  #0, #2, #4, #6, #8 and #10. The
> suffix ":N" specifies stride in the range, for
>                        example 0-10:3 is interpreted as 0,3,6,9 list.
>
> I don't think recursing can help in any way here...
>
> I've not found anything about the /64 of the comment, though...
>
> Cheers,
>
> Xabier Oneca_,,_
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>
>
> ------------------------------
>
> End of busybox Digest, Vol 172, Issue 7
> ***************************************
>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]