search for: numcores

...onst CPUWrapper& cpu) -{ - output << "Processor" << endl; - output << "CPU #: " << cpu.cpunum << endl; - output << "Core #: " << cpu.corenum << endl; - output << "Num. Cores: " << cpu.numcores << endl; - output << "Model: " << cpu.model << endl; - output << "Family: " << cpu.family << endl; - output << "CPU ID Level: " << cpu.cpuid_lvl << endl; - output << "Speed (Mhz): "...

...################################ cloneperms.sh ####################################### #!/bin/bash # Clone permissions & attributes from a template source to a target destination, # possibly recursing all subdirectories & files. Also supports parallelism. # # USAGE: cloneperms.sh [-r] [-p numcores] template target # # -r        : recurse all subdirectories. pointless if template & target are files # -p        : number of cores for parallel processing, defaults to 1. pointless if template & target are files # template  : source directory or file with permissions to clone # target   ...

I did a yum update on my management server and now the ovirt gui is no longer accessable. Is it supposed to just work or do I need to do something after the yum update? Justin.

On Sat, 2018-03-24 at 20:38 -0400, Ken McDonald via samba wrote: > > > By default, step 4 takes forever to run on large datasets because it > > uses named entities. My ultimate plan was to use the numeric > > user/group id's in that step instead of named ones so the Winbind cost > > is not incurred. Seems for the whole process, the calls to Winbind to > >

Removes node identification functionality from host-browser.rb and adds a new script, host-register.rb, that takes over that functionality. The chief difference is that host-browser used a simple TCP server setup to get data from the node, while host-register uses the qpid bus to do so. Specifically, it communicates with the matahari qmf agent added to the node in two related patchsets to node

...atahari has 1:N relationship between host and cpu objects, ovirt-server uses it by retrieving a list of cpus for each host: cpu_info = @qmfc.objects(:package => 'com.redhat.matahari', :class => 'cpu', 'host' => host.object_id) cpu properties used: cpunum corenum numcores vendor model family cpuid_lvl speed cache flags[0..251] New Matahari changed the model, here are CPU-related properties from 0.4.0 Host object, there isn't separate cpu class anymore: processors uint8 ReadOnly The number of physical CPUs. cores...

The purpose of this patch is to replace the identify function in host-browser.rb with a new script, host-register.rb. host-register.rb is a qmf ruby console that interfaces with the newly added matahari qmf agent on the ovirt node. While it stores node data in the database with the same behavior as the original host-browser implementation, it acquires the data using the amqp protocol (and

...ength > 255) ? "#{cpu.flags[0..251]}..." : cpu.flags - detail = Cpu.new( - 'cpu_number' => cpu.cpunum, - 'core_number' => cpu.corenum, - 'number_of_cores' => cpu.numcores, - 'vendor' => cpu.vendor, - 'model' => cpu.model.to_s, - 'family' => cpu.family.to_s, - 'cpuid_level' => cpu.cpuid_lvl, -...

Hi, thank you for sharing the system hierarchy model. IMHO it makes a lot of sense, although I don't know which of today's passes would make use of it. Here are my remarks. I am wondering how one could model the following features using this model, or whether they should be part of a performance model at all: * ARM's big.LITTLE * NUMA hierarchies (are the NUMA domains

...C) 2009 Red Hat, Inc. * Written by Arjun Roy <arroy at redhat.com> * * This program is free software; you can redistribute it and/or modify @@ -62,15 +62,15 @@ class CPUWrapper : public Manageable ~CPUWrapper() {} CPUWrapper(int cpunum__, - int corenum__, - int numcores__, - int model__, - int family__, - int cpuid_lvl__, - double speed__, - int cache__, - const string &vendor__, - const string &flags__) { + int corenum__, + int numcores__, + int model__, +...