| /linux/Documentation/filesystems/ |
| H A D | ocfs2.rst | 79 This means that if you lose your power, you will lose
|
| H A D | affs.rst | 35 gain above 4K seems not really worth the price, so you don't lose too
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | soft-dirty.rst | 34 there is still a scenario when we can lose soft dirty bits -- a task
|
| /linux/Documentation/power/ |
| H A D | swsusp.rst | 29 they won't be accessible after resume and you may lose data, as though
403 anything, not even read-only mount, or you are going to lose your
443 I suspend to disk, I can lose data unless the filesystem has been mounted
447 That's right ... if you disconnect that device, you may lose data.
448 In fact, even with "-o sync" you can lose data if your programs have
|
| /linux/net/rxrpc/ |
| H A D | io_thread.c | 212 static int lose; in rxrpc_input_packet() local
213 if ((lose++ & 7) == 7) { in rxrpc_input_packet()
|
| H A D | output.c | 695 static int lose; in rxrpc_send_data_packet() local
697 if ((lose++ & 7) == 7) { in rxrpc_send_data_packet()
|
| /linux/Documentation/input/joydev/ |
| H A D | joystick-api.rst | 135 is much safer since it can't lose sync with the driver. As you would
199 If time between reads is enough to fill the queue and lose an event,
|
| /linux/Documentation/hwmon/ |
| H A D | w83793.rst | 25 This parameter is not recommended, it will lose motherboard specific
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-inject.txt | 114 discards stack and register data from the samples. This will lose
|
| H A D | topdown.txt | 270 Since the individual metrics are only 8bit they lose precision for
|
| /linux/Documentation/networking/dsa/ |
| H A D | bcm_sf2.rst | 22 fail-over not to lose packets during a MoCA role re-election, as well as out of
|
| /linux/drivers/usb/core/ |
| H A D | Kconfig | 26 devices that lose power get reenumerated as if they had been
|
| /linux/arch/m68k/q40/ |
| H A D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 47 Returned by I2C adapters when they lose arbitration in master
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | vidtv.rst | 23 returned by the tuner, simulating a device that can lose/reacquire a lock
476 the demodulator can eventually lose the lock on the signal, since the tuner will
|
| /linux/Documentation/arch/x86/ |
| H A D | kernel-stacks.rst | 144 The most important property of this method is that we _never_ lose
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 176 statistics does not want to lose any statistics (those updated
|
| H A D | dm-clone.rst | 130 power is lost you may lose some recent writes. The metadata should always be
|
| H A D | cache.rst | 137 cache. If power is lost you may lose some recent writes. The metadata
|
| /linux/Documentation/input/devices/ |
| H A D | iforce-protocol.rst | 279 QUERY = 43 ('C')lose
|
| /linux/Documentation/trace/ |
| H A D | mmiotrace.rst | 83 Check that mmiotrace did not lose events due to a buffer filling up. Either::
|
| H A D | ring-buffer-design.rst | 74 will stop writing to the buffer. This will lose most recent events.
78 overwrite the older data. This will lose the oldest events.
|
| /linux/Documentation/fb/ |
| H A D | sstfb.rst | 175 patterns at the border of your windows (the pixels lose the lowest
|
| /linux/Documentation/networking/ |
| H A D | openvswitch.rst | 33 and existing protocols lose their prominence. For the Open vSwitch
|
| /linux/net/netfilter/ipvs/ |
| H A D | Kconfig | 60 small, otherwise you will lose performance on it. You can adapt the
|