Searched full:relatively (Results 1 – 25 of 574) sorted by relevance
12345678910>>...23
45 ret = LOS_TaskPriSet(g_testTaskID01, TASK_PRIO_TEST - 1); /* 1: Priority is relatively cheap */ in TaskF02()73 ICUNIT_ASSERT_EQUAL_VOID(ret, TASK_PRIO_TEST - 1, ret); /* 1: Priority is relatively cheap */ in TaskF01()
6 /* SH-4A can handle unaligned loads in a relatively neutered fashion. */
72 as the new base. The kernel is often in a relatively unstable state87 having been adequately tested are relatively low - as are the chances of209 It is relatively common to merge with the mainline toward the beginning of
6 make their 'diff' job easier if our code is relatively unmodified.
10 * relatively memory expensive (40 bytes on x86-64). If the object can be
9 that it has reached a relatively high error count and would probably
5 The regulator driver interface is relatively simple and designed to allow
47 * WRPKRU is relatively expensive compared to RDPKRU. in write_pkru()
17 skill levels; they are a relatively easy way to learn the kernel process in269 territory. Expect a lot of opinions and discussion for even relatively276 Python skills. The Sphinx toolchain is relatively small and well
17 skill levels; they are a relatively easy way to learn the kernel process in270 territory. Expect a lot of opinions and discussion for even relatively277 Python skills. The Sphinx toolchain is relatively small and well
48 SECURITY WARNING: It's relatively easy to eavesdrop all
9 " relatively sane even through a context switch.
26 relatively smooth sending rate is of importance.
26 * This example sits on a syscall, and the syscall ABI is relatively stable
34 * they fit together in one cache line. mn is relatively rarely
49 This is meant as a relatively simple mechanism that can be
202 1) simple, the number of threads should be relatively203 small and each thread function should be relatively
22 relatively narrow use case (jiffies in a relatively narrow HZ range)