Il 26/02/2013 15:04, Eduardo Habkost ha scritto:
>> > For me, the INI way to do multi-valued keys is still fine.
> Having multiple-valued keys (cpus=A,cpus=B,cpus=C) seems like the best
> intermediate solution while we don't have a decent generic syntax.
Even more so since:
1) we already support
On Tue, Feb 26, 2013 at 10:53:07AM +0100, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
> >> Eduardo Habkost writes:
> >>
> >> > This allows "," to be used a separator between each CPU range. Note
> >> > that commas
On Mon, Feb 25, 2013 at 10:04:07PM +0100, Andreas Färber wrote:
> Am 21.02.2013 21:57, schrieb Eduardo Habkost:
> > On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
> >> Eduardo Habkost writes:
> >>
> >>> This allows "," to be used a separator between each CPU range. Note
> >>>
Eduardo Habkost writes:
> On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>> > This allows "," to be used a separator between each CPU range. Note
>> > that commas inside key=value command-line options have to be escaped
>> > using ",,", so the
Am 21.02.2013 21:57, schrieb Eduardo Habkost:
> On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>>> This allows "," to be used a separator between each CPU range. Note
>>> that commas inside key=value command-line options have to be escaped
>>> usi
On Fri, Feb 22, 2013 at 11:04:24AM +0100, Markus Armbruster wrote:
> Markus Armbruster writes:
>
> > Anthony Liguori writes:
> >
> >> Markus Armbruster writes:
> >>
> >>> Eduardo Habkost writes:
> >>>
> This allows "," to be used a separator between each CPU range. Note
> that comma
Markus Armbruster writes:
> Anthony Liguori writes:
>
>> Markus Armbruster writes:
>>
>>> Eduardo Habkost writes:
>>>
This allows "," to be used a separator between each CPU range. Note
that commas inside key=value command-line options have to be escaped
using ",,", so the comm
On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > This allows "," to be used a separator between each CPU range. Note
> > that commas inside key=value command-line options have to be escaped
> > using ",,", so the command-line will look like:
> >
Anthony Liguori writes:
> Markus Armbruster writes:
>
>> Eduardo Habkost writes:
>>
>>> This allows "," to be used a separator between each CPU range. Note
>>> that commas inside key=value command-line options have to be escaped
>>> using ",,", so the command-line will look like:
>>>
>>> -nu
Markus Armbruster writes:
> Eduardo Habkost writes:
>
>> This allows "," to be used a separator between each CPU range. Note
>> that commas inside key=value command-line options have to be escaped
>> using ",,", so the command-line will look like:
>>
>> -numa node,cpus=A,,B,,C,,D
>
> This is
Eduardo Habkost writes:
> This allows "," to be used a separator between each CPU range. Note
> that commas inside key=value command-line options have to be escaped
> using ",,", so the command-line will look like:
>
> -numa node,cpus=A,,B,,C,,D
This is really, really ugly, and an embarrassme
This allows "," to be used a separator between each CPU range. Note
that commas inside key=value command-line options have to be escaped
using ",,", so the command-line will look like:
-numa node,cpus=A,,B,,C,,D
Note that the following format, currently used by libvirt:
-numa nodes,cpus=A,B
12 matches
Mail list logo
