qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Liu Jingqi <jingqi.liu@intel.com>,
	pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 5/7] numa: Extend the command-line to provide memory latency and bandwidth information
Date: Wed, 9 May 2018 08:16:28 -0500	[thread overview]
Message-ID: <7279dfe4-ca56-dbc7-c26f-ca566267a937@redhat.com> (raw)
In-Reply-To: <1525854998-14243-1-git-send-email-jingqi.liu@intel.com>

On 05/09/2018 03:36 AM, Liu Jingqi wrote:
> Add -numa hmat-lb option to provide System Locality Latency and
> Bandwidth Information. These memory attributes help to build
> System Locality Latency and Bandwidth Information Structure(s)
> in ACPI Heterogeneous Memory Attribute Table (HMAT).
> 
> Signed-off-by: Liu Jingqi <jingqi.liu@intel.com>
> ---

> +++ b/qapi/misc.json
> @@ -2705,7 +2705,7 @@
>   # Since: 2.1
>   ##
>   { 'enum': 'NumaOptionsType',
> -  'data': [ 'node', 'dist', 'cpu' ] }
> +  'data': [ 'node', 'dist', 'cpu', 'hmat-lb' ] }

Missing documentation for the new addition, particularly that it is 
'(since 2.13)'.


>   ##
> +# @NumaHmatLBOptions:
> +#
> +# Set the system locality latency and bandwidth information between Initiator and Target proximity Domains.

Long line here and elsewhere. Please keep this file wrapped below 80 
columns.

> +#
> +# @initiator: the Initiator Proximity Domain.
> +#
> +# @target: the Target Proximity Domain.
> +#
> +# @hierarchy: the Memory Hierarchy. Indicates the performance of memory or side cache.
> +#
> +# @level: indicates the level of side cache, if it's the performance of side cache.
> +#
> +# @data-type: presents the type of data, access/read/write latency or hit latency.
> +#
> +# @base-lat: the base unit for latency in nanosecondsbytes.

Is that supposed to be nanoseconds/bytes?

> +#
> +# @base-bw: the base unit for bandwidth in megabytes per second(MB/s).
> +#
> +# @latency: the value of latency based on Base Unit from @initiator to @target proximity domain.
> +#
> +# @bandwidth: the value of bandwidth based on Base Unit between @initiator to @target proximity domain.
> +#
> +# Since: 2.10

Not even close.  The soonest this could make it in is 2.13.

> +##
> +{ 'struct': 'NumaHmatLBOptions',
> +  'data': {
> +   'initiator': 'uint16',
> +   'target': 'uint16',
> +   'hierarchy': 'str',

Is this really a free-form string, or is it better as an enum type?

> +   '*level': 'uint8',
> +   'data-type': 'str',

Ditto.

> +   '*base-lat': 'uint64',
> +   '*base-bw': 'uint64',
> +   '*latency': 'uint16',
> +   '*bandwidth': 'uint16' }}
> +


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-05-09 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  8:36 [Qemu-devel] [PATCH v1 5/7] numa: Extend the command-line to provide memory latency and bandwidth information Liu Jingqi
2018-05-09 13:16 ` Eric Blake [this message]
2018-05-10  3:05   ` Liu, Jingqi

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=7279dfe4-ca56-dbc7-c26f-ca566267a937@redhat.com \
    --to=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jingqi.liu@intel.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).