All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH DOCDAY] introduce an xl man page in pod format
Date: Wed, 09 Nov 2011 15:47:29 +0100	[thread overview]
Message-ID: <4EBA9281.2020205@ts.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1111081832340.3519@kaball-desktop>

On 11/09/2011 03:41 PM, Stefano Stabellini wrote:
> On Fri, 28 Oct 2011, Ian Campbell wrote:
>> On Thu, 2011-10-27 at 17:19 +0100, Stefano Stabellini wrote:
>>> +=head1 CPUPOOLS COMMANDS
>>> +
>>> +Xen can group the physical cpus of a server in cpu-pools. Each physical CPU is
>>> +assigned at most to one cpu-pool. Domains are each restricted to a single
>>> +cpu-pool. Scheduling does not cross cpu-pool boundaries, so each cpu-pool has
>>> +an own scheduler.
>>> +Physical cpus and domains can be moved from one pool to another only by an
>>> +explicit command.
>>> +
>>> +=over 4
>>> +
>>> +=item B<cpupool-create>  [I<OPTIONS>] I<ConfigFile>
>>> +
>>> +Create a cpu pool based an I<ConfigFile>.
>>> +
>>> +B<OPTIONS>
>>> +
>>> +=over 4
>>> +
>>> +=item B<-f=FILE>, B<--defconfig=FILE>
>>> +
>>> +Use the given configuration file.
>>> +
>>> +=item B<-n>, B<--dryrun>
>>> +
>>> +Dry run - prints the resulting configuration.
>> Is this deprecated in favour of global -N option? I think it should be.
> Yeah, there is no point since we have a global option.
>
>>> +
>>> +=back
>>> +
>>> +=item B<cpupool-list>  [I<-c|--cpus>  I<cpu-pool>]
>>> +
>>> +List CPU pools on the host.
>>> +If I<-c>  is specified, B<xl>  prints a list of CPUs used by I<cpu-pool>.
>> Is cpu-pool a name or a number, or both? (this info would be useful in
>> the intro to the section I suppose).
> I think it is a name, but I would need a confirmation from Juergen.
>

Already specified by cs 24066.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2011-11-09 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 16:19 [PATCH DOCDAY] introduce an xl man page in pod format Stefano Stabellini
2011-10-28 10:10 ` Ian Campbell
2011-10-28 11:19   ` Juergen Gross
2011-10-28 10:43 ` Ian Campbell
2011-11-09 14:41   ` Stefano Stabellini
2011-11-09 14:47     ` Juergen Gross [this message]
2011-10-28 11:38 ` Ian Campbell
2011-10-28 12:51   ` Lars Kurth
2011-10-31  9:25 ` Ian Campbell
2011-10-31  9:32 ` Ian Campbell
2011-11-01 18:45 ` Ian Jackson
2011-11-02 19:34   ` Ian Campbell
2011-11-08 17:50     ` Stefano Stabellini
2011-11-08 19:57       ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EBA9281.2020205@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.