- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 227 for cpos (0.25 sec)
-
pkg/kubelet/cm/cpumanager/policy_options.go
// We picked "pcpu" because it the established docs hints at vCPU already. FullPhysicalCPUsOnly bool // Flag to evenly distribute CPUs across NUMA nodes in cases where more // than one NUMA node is required to satisfy the allocation. DistributeCPUsAcrossNUMA bool // Flag to ensure CPUs are considered aligned at socket boundary rather than // NUMA boundary AlignBySocket bool }
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed Sep 27 13:02:15 UTC 2023 - 5.1K bytes - Viewed (0) -
src/runtime/debug.go
// newprocs will be processed by startTheWorld newprocs = int32(n) startTheWorldGC(stw) return ret } // NumCPU returns the number of logical CPUs usable by the current process. // // The set of available CPUs is checked by querying the operating system // at process startup. Changes to operating system CPU allocation after // process startup are not reflected. func NumCPU() int { return int(ncpu)
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Sat May 11 20:38:24 UTC 2024 - 4.2K bytes - Viewed (0) -
src/cmd/vendor/golang.org/x/sys/unix/affinity_linux.go
// If pid is 0 the calling thread is used. func SchedSetaffinity(pid int, set *CPUSet) error { return schedAffinity(SYS_SCHED_SETAFFINITY, pid, set) } // Zero clears the set s, so that it contains no CPUs. func (s *CPUSet) Zero() { for i := range s { s[i] = 0 } } func cpuBitsIndex(cpu int) int { return cpu / _NCPUBITS } func cpuBitsMask(cpu int) cpuMask {
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed Feb 19 21:26:10 UTC 2020 - 1.9K bytes - Viewed (0) -
src/go/doc/comment/testdata/escape.txt
## Line -- markdown -- What the ~!@#$%^&\*()\_+-=\`{}|\[]\\:";',./\<>? \+ Line \- Line \* Line 999\. Line \## Line -- html -- <p>What the ~!@#$%^&*()_+-=`{}|[]\:";',./<>? <p>+ Line <p>- Line <p>* Line <p>999. Line
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Apr 11 16:31:40 UTC 2022 - 535 bytes - Viewed (0) -
cmd/update.go
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 18.7K bytes - Viewed (0) -
tensorflow/compiler/jit/node_matchers_test.cc
std::string::npos); EXPECT_NE(explanation.find("does not match expected: is empty"), std::string::npos); } { const std::string explanation = Explain(placeholder_d.node(), NodeWith(CtrlDeps(NodeWith()))); EXPECT_NE(explanation.find("ctrl_deps"), std::string::npos); EXPECT_NE(explanation.find("does not match expected: has 1 element and "
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Mon May 20 14:43:57 UTC 2024 - 9.1K bytes - Viewed (0) -
src/runtime/os_openbsd_arm.go
func checkgoarm() { // TODO(minux): FP checks like in os_linux_arm.go. // osinit not called yet, so ncpu not set: must use getncpu directly. if getncpu() > 1 && goarm < 7 { print("runtime: this system has multiple CPUs and must use\n") print("atomic synchronization instructions. Recompile using GOARM=7.\n") exit(1) } } //go:nosplit func cputicks() int64 {
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Dec 05 20:34:30 UTC 2023 - 662 bytes - Viewed (0) -
src/runtime/cputicks.go
//go:build !arm && !arm64 && !mips64 && !mips64le && !mips && !mipsle && !wasm package runtime // careful: cputicks is not guaranteed to be monotonic! In particular, we have // noticed drift between cpus on certain os/arch combinations. See issue 8976.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Mar 10 12:47:42 UTC 2023 - 437 bytes - Viewed (0) -
pkg/kubelet/cm/cpumanager/state/state_checkpoint_test.go
for pod := range tc.assignments { for container, set := range tc.assignments[pod] { state.SetCPUSet(pod, container, set) if cpus, _ := state.GetCPUSet(pod, container); !cpus.Equals(set) { t.Fatalf("state inconsistent, got %q instead of %q", set, cpus) } state.Delete(pod, container) if _, ok := state.GetCPUSet(pod, container); ok {
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed May 03 16:26:09 UTC 2023 - 10.9K bytes - Viewed (0) -
docs/pt/docs/tutorial/background-tasks.md
# Tarefas em segundo plano Você pode definir tarefas em segundo plano a serem executadas _ após _ retornar uma resposta. Isso é útil para operações que precisam acontecer após uma solicitação, mas que o cliente realmente não precisa esperar a operação ser concluída para receber a resposta. Isso inclui, por exemplo: - Envio de notificações por email após a realização de uma ação:
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Mon May 09 23:44:32 UTC 2022 - 5.3K bytes - Viewed (0)