Searched full:hundred (Results 1 – 25 of 38) sorted by relevance
12
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/ |
D | atmel,aic.yaml | 16 hundred and twenty-eight interrupt sources.
|
/linux-6.14.4/drivers/ptp/ |
D | Kconfig | 21 synchronization to within a few hundred nanoseconds.
|
/linux-6.14.4/Documentation/accounting/ |
D | psi.rst | 61 three hundred second windows, which gives insight into short term events
|
/linux-6.14.4/Documentation/maintainer/ |
D | feature-and-driver-maintainers.rst | 28 a subsystem could well have a hundred such drivers. Subsystem
|
/linux-6.14.4/arch/microblaze/mm/ |
D | fault.c | 165 * a few hundred bytes below the stack pointer (TBD). in do_page_fault()
|
/linux-6.14.4/Documentation/arch/x86/ |
D | pti.rst | 82 though.) Moves to CR3 are on the order of a hundred
|
/linux-6.14.4/fs/smb/server/ |
D | misc.c | 340 * Convert the NT UTC (based 1601-01-01, in hundred nanosecond units)
|
/linux-6.14.4/Documentation/filesystems/ |
D | affs.rst | 208 tested, though several hundred MB have been read and written using
|
/linux-6.14.4/drivers/firmware/google/ |
D | gsmi.c | 225 * hundred-ish usecs to ensure the SMI has triggered. in gsmi_exec() 988 * but the driver should spin for a hundred or so microseconds in gsmi_init()
|
/linux-6.14.4/drivers/gpu/drm/i915/gt/ |
D | intel_breadcrumbs.c | 185 * of hundred microseconds. If we are proactive and enable/disable in signal_irq_work()
|
/linux-6.14.4/Documentation/kbuild/ |
D | modules.rst | 227 consisting of several hundred lines, and here it really pays
|
/linux-6.14.4/Documentation/driver-api/ |
D | xillybus.rst | 95 There may be more than a hundred of these streams on a single IP core, but
|
/linux-6.14.4/drivers/comedi/drivers/ |
D | dmm32at.c | 518 /* should take 10 us to settle, here's a hundred */ in dmm32at_reset()
|
/linux-6.14.4/Documentation/fault-injection/ |
D | fault-injection.rst | 105 Note that one-failure-per-hundred is a very high error rate
|
/linux-6.14.4/Documentation/RCU/ |
D | checklist.rst | 57 but a hundred CPUs was unremarkable in 2017.
|
/linux-6.14.4/Documentation/process/ |
D | 2.Process.rst | 31 changesets with changes to several hundred thousand lines of code. 5.x is
|
/linux-6.14.4/drivers/firmware/efi/ |
D | cper.c | 45 * for the next few hundred years... in cper_next_record_id()
|
/linux-6.14.4/sound/firewire/bebob/ |
D | bebob_stream.c | 638 // NODATA packets. After several hundred cycles, it begins to multiplex event into in snd_bebob_stream_start_duplex()
|
/linux-6.14.4/Documentation/locking/ |
D | lockdep-design.rst | 324 is O(N^2), so even with just a few hundred lock-classes we'd have to do
|
/linux-6.14.4/Documentation/scheduler/ |
D | sched-util-clamp.rst | 46 coming few hundred milliseconds a computationally intensive scene is about to
|
/linux-6.14.4/drivers/input/mouse/ |
D | appletouch.c | 769 * several hundred times a second. in atp_complete_geyser_3_4()
|
/linux-6.14.4/arch/x86/kernel/ |
D | setup.c | 1032 * are known to corrupt low memory and several hundred kilobytes are not in setup_arch()
|
/linux-6.14.4/fs/smb/client/ |
D | netmisc.c | 932 * Convert the NT UTC (based 1601-01-01, in hundred nanosecond units)
|
/linux-6.14.4/Documentation/filesystems/xfs/ |
D | xfs-delayed-logging-design.rst | 920 limit here is in the order of several hundred concurrent transactions for a
|
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/mvm/ |
D | mac-ctxt.c | 612 * a few hundred microseconds (24 * 8 bits + PLCP time gives in iwl_mvm_set_fw_dtim_tbtt()
|
12