| /third_party/ltp/doc/ |
| H A D | C-Test-Case-Tutorial.asciidoc | 12 a tangent, just leave it for later and move on.
242 just a single string of text with no spaces. The second column, which can
244 is just the executable name, but some tests also take arguments (the LTP has a
404 we are usually just copying headers required for interacting with the Kernel's
433 For the time being though we shall just ignore this. All you need to know for
463 return. This is mainly just for convenience, although it potentially could
521 have control over. Deciding where to create the files is easy, we just create
554 macros such as +STATX_BASIC_STATS+. However for the time being we have just
594 file +file_to_stat+. Because we have set +.needs_tmpdir+, we can just create
676 +TBROK+. Instead they just prin
[all...] |
| /third_party/node/deps/v8/src/objects/ |
| H A D | js-date-time-format.cc | 627 isolate, options, factory->locale_string(), locale, Just(kDontThrow)); in ResolvedOptions()
634 isolate, options, factory->calendar_string(), calendar, Just(kDontThrow)); in ResolvedOptions()
642 Just(kDontThrow)); in ResolvedOptions()
647 isolate, options, factory->timeZone_string(), timezone, Just(kDontThrow)); in ResolvedOptions()
657 date_time_format->HourCycleAsString(), Just(kDontThrow)); in ResolvedOptions()
666 Just(kDontThrow)); in ResolvedOptions()
675 Just(kDontThrow)); in ResolvedOptions()
698 factory->NewNumberFromInt(fsd), Just(kDontThrow)); in ResolvedOptions()
709 Just(kDontThrow)); in ResolvedOptions()
723 Just(kDontThro in ResolvedOptions()
[all...] |
| /third_party/python/Doc/install/ |
| H A D | index.rst | 71 :file:`README.txt` or possibly just :file:`README`, which should explain that
83 modules you've just downloaded: Run the command above. Unless you need to
108 into. For example, if you've just downloaded a module source distribution
181 platform and Python version. The first form, with just a :file:`lib` directory,
206 If you don't choose an installation directory---i.e., if you just run ``setup.py
242 simple commands. Under Unix, just type ``python`` at the shell prompt. Under
366 Unix, lazy typists can just type a tilde (``~``); the :command:`install` command
423 base, which is used for platform-specific files. (Currently, this just means
496 :ref:`inst-alt-install` just don't do what you want. You might want to tweak just
[all...] |
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Analysis/ |
| H A D | BasicAliasAnalysis.cpp | 222 // - just give up. It is up to caller to make sure the pointer is pointing in isObjectSmallerThan()
292 // If it's a constant, just convert it to an offset and remove the variable. in GetLinearExpression()
375 // bits of a sign or zero extended value - just scales and offsets. The in GetLinearExpression()
387 // by just incrementing the number of bits we've extended by. in GetLinearExpression()
461 /// depth (MaxLookupSearchDepth). When DataLayout not is around, it just looks
645 // If the chain of expressions is too deep, just return early. in DecomposeGEPExpression()
777 // We can bound the aliasing properties of memset_pattern16 just as we can in isWriteOnlyParam()
847 // through this once, so just return the cached results. Notably, when this in alias()
1246 // The same applies if (b) is based on a GlobalVariable. Note that just being
1383 // just th in aliasGEP()
[all...] |
| /kernel/linux/linux-5.10/Documentation/process/ |
| H A D | submitting-patches.rst | 81 complete patch description and justification for it. Don't just
105 If you want to refer to a specific commit, don't just refer to the
279 No MIME, no links, no compression, no attachments. Just plain text
396 then you just add a line saying::
403 Some people also put extra tags at the end. They'll just be ignored for
404 now, but you can do this to mark internal company procedures or just
429 one subsystem maintainer then this usually indicates acknowledgement of just
643 it may not be necessary to include _all_ of the compile failures; just
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| H A D | events.rst | 272 effect) trace output. Only filters that reference just the common
353 but just will not be traced, unless of course it's actually enabled.
388 For ease of use, writing to the trigger file using '>' currently just
403 That is, the tracepoint will be called, but just will not be traced.
683 just the first four sched_fields::
736 All vals should be cast to u64, and string vals are just pointers to
761 The 'vals' array is just an array of u64, the number of which must
765 All vals should be cast to u64, and string vals are just pointers to
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 74 The CPU will report a quiescent state just after enqueuing the task because
86 | Why not just have the expedited grace period check the state of all |
108 Please note that this is just the overall flow: Additional complications
191 | CPUs that were once online? Why not just have a single set of masks |
225 the mask of CPUs to be IPIed and again just before IPIing a CPU (both
245 bitmask of CPUs that must be IPIed, just before sending each IPI, and
436 stalls just as normal grace periods do.
441 | But why not just let the normal grace-period machinery detect the |
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 118 - Do not enable PCI DAC cycles. This just broke support for
268 (Size is limited to 8 for now, but a constant is just to be
338 Just use 2 tag counters in flip/flop and switch to the other
405 happen, we just discard the data if use_sg is not zero.
412 Hopefully, the driver is now unbreakable or may-be, it is just
428 and I just translated it into ncr53c8xx syntax.
541 - Damned! I just broke the driver for Alpha by leaving a stale
573 Just give a try using "sym53c" and "sym53c8xx" instead of "ncr53c"
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 118 - Do not enable PCI DAC cycles. This just broke support for
268 (Size is limited to 8 for now, but a constant is just to be
338 Just use 2 tag counters in flip/flop and switch to the other
405 happen, we just discard the data if use_sg is not zero.
412 Hopefully, the driver is now unbreakable or may-be, it is just
428 and I just translated it into ncr53c8xx syntax.
541 - Damned! I just broke the driver for Alpha by leaving a stale
573 Just give a try using "sym53c" and "sym53c8xx" instead of "ncr53c"
|
| /kernel/linux/linux-6.6/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 74 The CPU will report a quiescent state just after enqueuing the task because
86 | Why not just have the expedited grace period check the state of all |
108 Please note that this is just the overall flow: Additional complications
191 | CPUs that were once online? Why not just have a single set of masks |
225 the mask of CPUs to be IPIed and again just before IPIing a CPU (both
245 bitmask of CPUs that must be IPIed, just before sending each IPI, and
436 stalls just as normal grace periods do.
441 | But why not just let the normal grace-period machinery detect the |
|
| /kernel/linux/linux-5.10/drivers/md/bcache/ |
| H A D | request.c | 98 * is bigger than an empty write: If we just return -ENOMEM here, in bch_keylist_realloc()
144 * Our data write just errored, which means we've got a bunch of keys to in bch_data_insert_error()
148 * that region of the cache - so, if we just strip off all the pointers in bch_data_insert_error()
149 * from the keys we'll accomplish just that. in bch_data_insert_error()
259 * But if it's not a writeback write we'd rather just bail out if in bch_data_insert_start()
268 * we wait for buckets to be freed up, so just invalidate the in bch_data_insert_start()
275 * From a cache miss, we can just insert the keys for the data in bch_data_insert_start()
827 * First, we copy the data we just read from cache_bio's bounce buffers in cached_dev_read_done()
|
| /kernel/linux/linux-5.10/net/sctp/ |
| H A D | sm_sideeffect.c | 288 /* Is this association really dead and just waiting around for in sctp_generate_timeout_event()
426 /* Is this structure just waiting around for us to actually in sctp_generate_proto_unreach_event()
672 * just return the error and stop processing the stack. in sctp_cmd_process_init()
940 * destination address (we use active path instead of primary path just
1351 * The argument tells us whether to just count in sctp_cmd_interpreter()
1381 * there is an error just return to the outter in sctp_cmd_interpreter()
1537 * halts when we call add_timer. So here, instead of just starting in sctp_cmd_interpreter()
1538 * a timer, if the timer is already started, and just mod in sctp_cmd_interpreter()
|
| /kernel/linux/linux-6.6/kernel/locking/ |
| H A D | rwsem.c | 102 * just in case we need to use up more of the reader bits for other purpose
164 * Note that the owner value just indicates the task has owned the rwsem
269 * Return just the real task structure pointer of the owner
303 * and a writer has just released the lock. So another writer may steal
803 * The limit is capped to a maximum of 25us (30 readers). This is just
899 * task just comes in and acquire the lock before in rwsem_optimistic_spin()
1166 * has just released the lock, OWNER_NULL will be returned. in rwsem_down_write_slowpath()
1222 * - just wake up any readers at the front of the queue
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/i915/display/ |
| H A D | intel_sprite.c | 183 * Let's assume the case with just two sprites enabled also in vlv_plane_ratio()
240 * downscaling factor here. We ignore that and just consider in vlv_plane_min_cdclk()
419 * the control register just before the surface register. in vlv_sprite_update_arm()
539 * downscaling factor here. We ignore that and just consider in ivb_plane_min_cdclk()
559 * downscaling factor here. We ignore that and just consider in ivb_sprite_min_cdclk()
842 * the control register just before the surface register. in ivb_sprite_update_arm()
899 * downscaling factor here. We ignore that and just consider in g4x_sprite_min_cdclk()
1161 * the control register just before the surface register. in g4x_sprite_update_arm()
|
| /kernel/linux/linux-6.6/drivers/md/bcache/ |
| H A D | request.c | 98 * is bigger than an empty write: If we just return -ENOMEM here, in bch_keylist_realloc()
144 * Our data write just errored, which means we've got a bunch of keys to in bch_data_insert_error()
148 * that region of the cache - so, if we just strip off all the pointers in bch_data_insert_error()
149 * from the keys we'll accomplish just that. in bch_data_insert_error()
259 * But if it's not a writeback write we'd rather just bail out if in bch_data_insert_start()
268 * we wait for buckets to be freed up, so just invalidate the in bch_data_insert_start()
275 * From a cache miss, we can just insert the keys for the data in bch_data_insert_start()
828 * First, we copy the data we just read from cache_bio's bounce buffers in cached_dev_read_done()
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylake/ |
| H A D | memory.json | 96 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer than just the memory latency.",
108 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer than just the memory latency.",
120 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer than just the memory latency.",
132 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer than just the memory latency.",
144 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.",
156 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 512 cycles. Reported latency may be longer than just the memory latency.",
168 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 64 cycles. Reported latency may be longer than just the memory latency.",
180 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | memory.json | 96 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer than just the memory latency.",
108 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer than just the memory latency.",
120 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer than just the memory latency.",
132 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer than just the memory latency.",
144 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.",
156 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 512 cycles. Reported latency may be longer than just the memory latency.",
168 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 64 cycles. Reported latency may be longer than just the memory latency.",
180 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.",
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | uncore-memory.json | 224 "PublicDescription": "CKE_ON_CYCLES by Rank : DIMM ID : Number of cycles spent in CKE ON mode. The filter allows you to select a rank to monitor. If multiple ranks are in CKE ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Multiple counters will need to be used to track multiple ranks simultaneously. There is no distinction between the different CKE modes (APD, PPDS, PPDF). This can be determined based on the system programming. These events should commonly be used with Invert to get the number of cycles in power saving mode. Edge Detect is also useful here. Make sure that you do NOT use Invert with Edge Detect (this just confuses the system and is not necessary).",
233 "PublicDescription": "CKE_ON_CYCLES by Rank : DIMM ID : Number of cycles spent in CKE ON mode. The filter allows you to select a rank to monitor. If multiple ranks are in CKE ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Multiple counters will need to be used to track multiple ranks simultaneously. There is no distinction between the different CKE modes (APD, PPDS, PPDF). This can be determined based on the system programming. These events should commonly be used with Invert to get the number of cycles in power saving mode. Edge Detect is also useful here. Make sure that you do NOT use Invert with Edge Detect (this just confuses the system and is not necessary).",
242 "PublicDescription": "CKE_ON_CYCLES by Rank : DIMM ID : Number of cycles spent in CKE ON mode. The filter allows you to select a rank to monitor. If multiple ranks are in CKE ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Multiple counters will need to be used to track multiple ranks simultaneously. There is no distinction between the different CKE modes (APD, PPDS, PPDF). This can be determined based on the system programming. These events should commonly be used with Invert to get the number of cycles in power saving mode. Edge Detect is also useful here. Make sure that you do NOT use Invert with Edge Detect (this just confuses the system and is not necessary).",
251 "PublicDescription": "CKE_ON_CYCLES by Rank : DIMM ID : Number of cycles spent in CKE ON mode. The filter allows you to select a rank to monitor. If multiple ranks are in CKE ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Multiple counters will need to be used to track multiple ranks simultaneously. There is no distinction between the different CKE modes (APD, PPDS, PPDF). This can be determined based on the system programming. These events should commonly be used with Invert to get the number of cycles in power saving mode. Edge Detect is also useful here. Make sure that you do NOT use Invert with Edge Detect (this just confuses the system and is not necessary).",
379 "PublicDescription": "Read Pending Queue Full Cycles : Counts the number of cycles when the Read Pending Queue is full. When the RPQ is full, the HA will not be able to issue any additional read requests into the iMC. This count should be similar count in the HA which tracks the number of cycles that the HA has no RPQ credits, just somewhat smaller to account for the credit return overhead. We generally do not expect to see RPQ become full except for potentially during Write Major Mode or while running with slow DRAM. This event only tracks non-ISOC queue entries.",
387 "PublicDescription": "Read Pending Queue Full Cycles : Counts the number of cycles when the Read Pending Queue is full. When the RPQ is full, the HA will not be able to issue any additional read requests into the iMC. This count should be similar count in the HA which tracks the number of cycles that the HA has no RPQ credits, just somewhat smaller to account for the credit return overhead. We generally do not expect to see RPQ become full except for potentially during Write Major Mode or while running with slow DRAM. This event only tracks non-ISOC queue entries.",
447 "PublicDescription": "Write Pending Queue Full Cycles : Counts the number of cycles when the Write Pending Queue is full. When the WPQ is full, the HA will not be able to issue any additional write requests into the iMC. This count should be similar count in the CHA which tracks the number of cycles that the CHA has no WPQ credits, just somewhat smaller to account for the credit return overhead.",
455 "PublicDescription": "Write Pending Queue Full Cycles : Counts the number of cycles when the Write Pending Queue is full. When the WPQ is full, the HA will not be able to issue any additional write requests into the iMC. This count should be similar count in the CHA which tracks the number of cycles that the CHA has no WPQ credits, just somewhat smaller to account for the credit return overhead.",
|
| /kernel/linux/linux-6.6/net/sctp/ |
| H A D | sm_sideeffect.c | 288 /* Is this association really dead and just waiting around for in sctp_generate_timeout_event()
426 /* Is this structure just waiting around for us to actually in sctp_generate_proto_unreach_event()
704 * just return the error and stop processing the stack. in sctp_cmd_process_init()
950 * destination address (we use active path instead of primary path just
1356 * The argument tells us whether to just count in sctp_cmd_interpreter()
1386 * there is an error just return to the outter in sctp_cmd_interpreter()
1542 * halts when we call add_timer. So here, instead of just starting in sctp_cmd_interpreter()
1543 * a timer, if the timer is already started, and just mod in sctp_cmd_interpreter()
|
| /third_party/curl/docs/ |
| H A D | TheArtOfHttpScripting.md | 59 Many times you may wonder what exactly is taking all the time, or you just
143 The path part is just sent off to the server to request that it sends back
180 is probably to just use one, but you can specify any amount of URLs. Yes
231 the data you send. You cannot just invent something out of the air.
256 To make curl do the GET form post for you, just enter the expected created
328 in, they are not displayed to the user and they get passed along just as all
499 cookies. Cookies are just names with associated contents. The cookies are
647 While not strictly just HTTP related, it still causes a lot of people
|
| /third_party/mesa3d/src/compiler/nir/ |
| H A D | nir_lower_shader_calls.c | 301 /* TODO: If a SSA def is filled more than once, we probably want to just in spill_ssa_defs_and_lower_shader_calls()
448 * just re-compute instead of fetching from memory. in spill_ssa_defs_and_lower_shader_calls()
452 /* For now, we just make a note of this new SSA def. We'll in spill_ssa_defs_and_lower_shader_calls()
648 * where it's just if-ladders. in duplicate_loop_bodies()
874 * just skip it and consider we're after the cursor. in flatten_resume_if_ladder()
969 * resume_node have been copied before the cursor. We just need to in flatten_resume_if_ladder()
985 * everything after it in the entire list (not just the one block), and in flatten_resume_if_ladder()
1050 * of all those pesky registers we just added. in lower_resume()
|
| /third_party/musl/src/hilog/linux/ |
| H A D | output_p.inl | 250 /* Compatibility code for "%I" just print I */
601 /* Compatibility code for "%I" just print I */
626 /*if it's a private arg, just write <priate> to stream*/
651 /*if it's a private arg, just write <priate> to stream*/
676 /*if it's a private arg, just write <priate> to stream*/
811 /* bufferSize is large enough,just validation the return value */
988 /*if it's a private arg, just write <priate> to stream*/
1147 /*if it's a private arg, just write <priate> to stream*/
|
| /third_party/musl/porting/linux/user/src/hilog/ |
| H A D | output_p.inl | 250 /* Compatibility code for "%I" just print I */
601 /* Compatibility code for "%I" just print I */
626 /*if it's a private arg, just write <priate> to stream*/
651 /*if it's a private arg, just write <priate> to stream*/
676 /*if it's a private arg, just write <priate> to stream*/
811 /* bufferSize is large enough,just validation the return value */
988 /*if it's a private arg, just write <priate> to stream*/
1147 /*if it's a private arg, just write <priate> to stream*/
|
| /third_party/node/deps/npm/man/man5/ |
| H A D | package-json.5 | 6 This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a JavaScript object literal.
247 You can also provide a \fB.npmignore\fR file in the root of your package or in subdirectories, which will keep files from being included. At the root of your package it will not override the "files" field, but in subdirectories it will. The \fB.npmignore\fR file works just like a \fB.gitignore\fR. If there is a \fB.gitignore\fR file, and \fB.npmignore\fR is missing, \fB.gitignore\fR's contents will be used instead.
355 If you have a single executable, and its name should be the name of the package, then you can just supply it as a string. For example:
557 \fB""\fR (just an empty string) Same as \fB*\fR
647 As of version 1.1.65, you can refer to GitHub urls as just "foo": "user/foo-project". Just as with git URLs, a \fBcommit-ish\fR suffix can be included. For example:
811 If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then you may put it in the \fBoptionalDependencies\fR object. This is a map of package name to version or url, just like the \fBdependencies\fR object. The difference is that build failures do not cause installation to fail. Running \fBnpm install
979 You can also block instead of allowing operating systems, just prepend the blocked os with a '!':
|
| H A D | npm-json.5 | 6 This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a JavaScript object literal.
247 You can also provide a \fB.npmignore\fR file in the root of your package or in subdirectories, which will keep files from being included. At the root of your package it will not override the "files" field, but in subdirectories it will. The \fB.npmignore\fR file works just like a \fB.gitignore\fR. If there is a \fB.gitignore\fR file, and \fB.npmignore\fR is missing, \fB.gitignore\fR's contents will be used instead.
355 If you have a single executable, and its name should be the name of the package, then you can just supply it as a string. For example:
557 \fB""\fR (just an empty string) Same as \fB*\fR
647 As of version 1.1.65, you can refer to GitHub urls as just "foo": "user/foo-project". Just as with git URLs, a \fBcommit-ish\fR suffix can be included. For example:
811 If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then you may put it in the \fBoptionalDependencies\fR object. This is a map of package name to version or url, just like the \fBdependencies\fR object. The difference is that build failures do not cause installation to fail. Running \fBnpm install
979 You can also block instead of allowing operating systems, just prepend the blocked os with a '!':
|