| /Linux-v6.6/fs/ubifs/ |
| D | commit.c | 12 * This file implements functions that manage the running of the commit process.
14 * commit and those functions are called here.
16 * The commit is the process whereby all updates to the index and LEB properties
21 * The commit is split into two parts named "commit start" and "commit end".
22 * During commit start, the commit process has exclusive access to the journal
23 * by holding the commit semaphore down for writing. As few I/O operations as
24 * possible are performed during commit start, instead the nodes that are to be
25 * written are merely identified. During commit end, the commit semaphore is no
27 * to use the file system while the bulk of the commit I/O is performed. The
28 * purpose of this two-step approach is to prevent the commit from causing any
[all …]
|
| D | log.c | 161 * %-EAGAIN if commit is required, and a negative error code in case of
205 dbg_log("bud bytes %lld (%lld max), require commit", in ubifs_add_bud_to_log()
213 * If the journal is full enough - start background commit. Note, it is in ubifs_add_bud_to_log()
219 dbg_log("bud bytes %lld (%lld max), initiate BG commit", in ubifs_add_bud_to_log()
331 * If the commit does not finish, the recovery will need in remove_buds()
334 * commit i.e. do not allow them to be garbage in remove_buds()
344 * ubifs_log_start_commit - start commit.
348 * The commit operation starts with writing "commit start" node to the log and
350 * the commit has been finished. The commit start and reference nodes are
351 * written in one go to the nearest empty log LEB (hence, when commit is
[all …]
|
| D | tnc_commit.c | 17 * make_idx_node - make an index node for fill-the-gaps method of TNC commit.
156 * find_old_idx - find an index node obsoleted since the last commit start.
218 * method of TNC commit.
326 * get_leb_cnt - calculate the number of empty LEBs needed to commit.
328 * @cnt: number of znodes to commit
330 * This function returns the number of empty LEBs needed to commit @cnt znodes
349 * @cnt: number of dirty znodes to commit.
352 * method of TNC commit.
387 /* Try to commit anyway */ in layout_in_gaps()
556 * layout_commit - determine positions of index nodes to commit.
[all …]
|
| D | orphan.c | 15 * (unlinked) and then a commit is run. In the normal course of events the inode
37 * the commit is run, are written to the orphan area in 1 or more orphan nodes.
233 * ubifs_orphan_start_commit - start commit of orphans.
236 * Start commit of orphans.
255 dbg_cmt("%d orphans to commit", c->cmt_orphans); in ubifs_orphan_start_commit()
387 /* Mark the last node of the commit */ in write_orph_node()
399 * write_orph_nodes - write orphan nodes until there are no more to commit.
403 * This function writes orphan nodes for all the orphans to commit. On success,
433 * to commit. The list is in the order that the orphans were added, and the
478 * commit_orphans - commit orphans.
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/ |
| D | drm_atomic_helper.c | 52 * This helper library provides implementations of check and commit functions on
59 * drm_atomic_helper_check() and for the commit callback with
333 * atomic check or commit, this is racy. But that's OK: all we care in update_connector_routing()
1244 * Drivers can use this for building their own atomic commit if they don't have
1399 * drm_atomic_helper_commit_modeset_disables - modeset commit to disable outputs
1407 * drm_atomic_helper_commit_planes(), which is what the default commit function
1446 * drm_atomic_helper_commit_modeset_enables - modeset commit to enable outputs
1454 * drm_atomic_helper_commit_planes(), which is what the default commit function
1486 else if (funcs->commit) in drm_atomic_helper_commit_modeset_enables()
1487 funcs->commit(crtc); in drm_atomic_helper_commit_modeset_enables()
[all …]
|
| /Linux-v6.6/scripts/ |
| D | checkkconfigsymbols.py | 53 parser.add_argument('-c', '--commit', dest='commit', action='store',
55 help="check if the specified commit (hash) introduces "
87 if args.commit and args.diff:
94 if args.commit or args.diff:
103 if args.commit:
104 if args.commit.startswith('HEAD'):
105 sys.exit("The --commit option can't use the HEAD ref")
125 if args.sim and not args.commit and not args.diff:
137 if args.commit or args.diff:
140 # get commit range
[all …]
|
| /Linux-v6.6/tools/testing/ktest/examples/include/ |
| D | patchcheck.conf | 4 # commit between the two. The build test will look at what files the
5 # commit has touched, and if any of those files produce a warning, then
9 # PATCH_START is the commit to begin with and PATCH_END is the commit
11 # and then testing each commit and doing a git rebase --continue.
38 # Change PATCH_TEST to run some test for each patch. Each commit that is
52 # but you do not care about it, set IGNORE_WARNINGS to that commit(s)
59 # touched by the commit. To detect these kinds of warnings, you
73 # Checkout the commit before the patches to test,
84 # from this commit instead of the PATCH_START commit.
|
| D | bisect.conf | 21 # You must set the commit that was considered good (git bisect good)
23 # You must set the commit that was considered bad (git bisect bad)
35 # set to 1 will check both that the good commit works and the bad
36 # commit fails. If you only want to check one or the other,
58 # not want to continue the bisect on that commit that failed.
59 # By setting BISECT_START to a new commit. ktest.pl will checkout
60 # that commit after it has performed the 'git bisect replay' but
66 # if the commit was good or bad. Instead, it will ask you to tell
67 # it if the current commit was good. In the mean time, you could
71 # the git bisect. You can even change what commit it is currently at.
|
| /Linux-v6.6/fs/jfs/ |
| D | jfs_txnmgr.h | 27 u16 xflag; /* tx commit type */
28 u16 flag; /* tx commit state */
42 /* commit management */
43 struct list_head cqueue; /* commit queue list */
44 s32 clsn; /* commit lsn */
46 s32 pn; /* commit record log page number */
47 s32 eor; /* commit record eor */
48 wait_queue_head_t gcwait; /* group commit event list:
50 * event for group commit completion.
61 /* commit flags: tblk->xflag */
[all …]
|
| D | jfs_logmgr.c | 23 * group commit:
24 * transactions which wrote COMMIT records in the same in-memory
28 * TBD lazy commit:
30 * containing it COMMIT is paged out when it becomes full;
34 * . a per log lock serialize group commit.
86 * log group commit serialization (per log)
193 uint commit; /* # of commit */ member
276 * commit time to allow forwarding log syncpt past log in lmLog()
337 * PARAMETER: cd - commit descriptor
496 INCREMENT(lmStat.commit); /* # of commit */ in lmWriteRecord()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/tc-testing/tc-tests/actions/ |
| D | ct.json | 124 "name": "Try ct with zone, commit",
137 "cmdUnderTest": "$TC actions add action ct zone 404 commit index 42",
140 "matchPattern": "action order [0-9]*: ct commit zone 404 pipe.*index 42 ref",
148 "name": "Try ct with zone, commit, mark",
161 "cmdUnderTest": "$TC actions add action ct zone 404 commit mark 0x42 index 42",
164 "matchPattern": "action order [0-9]*: ct commit mark 66 zone 404 pipe.*index 42 ref",
172 "name": "Try ct with zone, commit, mark, nat",
185 …"cmdUnderTest": "$TC actions add action ct zone 404 commit mark 0x42 nat src addr 5.5.5.7 index 42…
188 …"matchPattern": "action order [0-9]*: ct commit mark 66 zone 404 nat src addr 5.5.5.7 pipe.*index …
209 …"cmdUnderTest": "$TC actions add action ct commit nat src addr 5.5.5.7-5.5.6.0 port 1000-2000 inde…
[all …]
|
| /Linux-v6.6/Documentation/filesystems/ext4/ |
| D | journal.rst | 15 read-write-erases) before erasing the commit record. Should the system
17 way to the latest commit record, guaranteeing the atomicity of whatever
32 help reduce commit latency significantly. The default ``data=ordered``
33 mode works by logging metadata blocks to the journal. In fast commit
35 affected metadata in fast commit space that is shared with JBD2.
36 Once the fast commit area fills in or if fast commit is not possible
37 or if JBD2 commit timer goes off, Ext4 performs a traditional full commit.
38 A full commit invalidates all the fast commits that happened before
39 it and thus it makes the fast commit area empty for further fast
75 commit. If there is no commit record (or the checksums don't match), the
[all …]
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.rst | 60 commit boundaries, whilst "one shot" transactions are for a single atomic
198 that the common/fast path transaction will commit two linked transactions in a
259 sleep during the transaction commit process waiting for new log space to become
263 then wake up transaction commit in progress.
280 after the commit completes. Once the commit completes, we can sleep waiting for
334 implement long-running, multiple-commit permanent transactions.
457 the delayed logging tracking lock to commit the transaction. However, the
467 transaction commit while the item is locked in the transaction. Instead of
475 rewriting can all be done while the object is locked during transaction commit,
560 in transaction commit order, so when an object is relogged it is removed from
[all …]
|
| D | journalling.rst | 66 A jbd2_journal_flush() may be called at any time to commit and
107 journal commit callback for this purpose.
109 With journal commit callbacks you can ask the journalling layer to call
114 called after each transaction commit. You can also use
142 `journal->j_fc_cleanup_cb`: Cleanup function called after every full commit and
143 fast commit.
145 `journal->j_fc_replay_cb`: Replay function called for replay of fast commit
150 :c:func:`jbd2_fc_begin_commit()`. Once a fast commit is done, the client
153 commit immediately after stopping the fast commit it can do so by calling
154 :c:func:`jbd2_fc_end_commit_fallback()`. This is useful if fast commit operation
[all …]
|
| /Linux-v6.6/fs/ext4/ |
| D | fast_commit.c | 24 * don't have replay code, fast commit falls back to full commits.
44 * Commit Operation
48 * to disk during the commit operation. We also maintain a list of inodes
49 * that need to be committed during a fast commit in another in memory queue of
50 * inodes. During the commit operation, we commit in the following order:
55 * [4] Commit all the directory entry updates in the fast commit space
56 * [5] Commit all the changed inode structures
62 * update. If such an ongoing update is present, fast commit waits for it to
66 * Fast Commit Ineligibility
70 * attributes). Fast commit ineligibility is marked by calling
[all …]
|
| D | fast_commit.h | 11 /* Fast commit tags */
24 /* On disk fast commit tlv value structures */
26 /* Fast commit on disk tag length structure */
77 * Fast commit status codes
87 * Fast commit ineligiblity reasons:
106 * system used by fast commit code.
131 * Physical block regions added to different inodes due to fast commit
144 * Fast commit replay state.
|
| /Linux-v6.6/Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 115 in-and-around commit 7a6c8ae ("Fix text that describes vfmv.v.f
128 changes to interrupts as frozen at commit ccbddab ("Merge pull
135 behavioural changes to interrupts as frozen at commit ccbddab
141 and mode-based filtering as ratified at commit 01d1df0 ("Add ability
147 ratified at commit 3f9ed34 ("Add ability to manually trigger
171 acceleration instructions as ratified at commit 6d33919 ("Merge pull
178 as ratified at commit 6d33919 ("Merge pull request #158 from
184 multiplication as ratified at commit 6d33919 ("Merge pull request
190 instructions as ratified at commit 6d33919 ("Merge pull request #158
196 ratified in commit 3dd606f ("Create cmobase-v1.0.pdf") of riscv-CMOs.
[all …]
|
| /Linux-v6.6/include/linux/ |
| D | jbd2.h | 46 * The default maximum commit age, in seconds.
150 * Commit block header for storing transactional checksums:
239 __be32 s_sequence; /* first commit ID expected in log */
267 __be32 s_num_fc_blks; /* Number of fast commit blocks */
383 * Commit of the inode data in progress. We use this flag to protect us from
388 /* Write allocated dirty buffers in this inode before commit */
390 /* Wait for outstanding data writes for this inode before commit */
395 * ordered mode present in a transaction so that we can sync them during commit.
525 * COMMIT: All data on disk, writing commit record
580 * Where in the log does this transaction's commit start? [no locking]
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/msm/ |
| D | msm_kms.h | 35 * Atomic commit handling:
45 * for example SMP blocks to release after commit completes. Ie.
54 * commit related methods.
63 * Prepare for atomic commit. This is called after any previous
64 * (async or otherwise) commit has completed.
69 * Flush an atomic commit. This is called after the hardware
78 * commit (ie. don't just wait for a vblank), as it will also
80 * "async" commit has completed.
85 * Clean up after commit is completed. This is called after
87 * post-commit cleanup.
[all …]
|
| /Linux-v6.6/Documentation/trace/ |
| D | ring-buffer-design.rst | 191 It is possible that the page swapped is the commit page and the tail page,
196 reader page commit page tail page
230 commit page
233 The commit page only is updated by the outermost writer in the
235 commit page.
251 +---------+ <--- given back to writer (current commit)
257 Write commit::
264 +---------+ <--- next position for write (current commit)
274 +---------+ <-- current commit
286 +---------+ <--(last full commit)
[all …]
|
| /Linux-v6.6/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-check-branches.sh | 17 # see which commit came from which branch.
62 # Each pass through this loop tests one commit.
67 echo ' --- commit ' $i from branch $gitbr
73 # Test the specified commit.
75 echo git checkout return code: $? "(Commit $ntry: $i)"
78 echo kvm.sh return code $ret for commit $i from branch $gitbr
92 # Go back to the original commit.
|
| /Linux-v6.6/include/drm/ |
| D | drm_atomic.h | 37 * This structure is used to track pending modeset changes and atomic commit on
45 * atomic commit thread hardware
76 * DRM CRTC for this commit.
94 * commit is sent to userspace, or when an out-fence is singalled. Note
106 * Will be signalled when all hw register changes for this commit have
155 * used by the free code to remove the second reference if commit fails.
170 * @commit:
172 * A reference to the CRTC commit object that is kept for use by
175 * concurrent commit won't free a commit object that is still in use.
177 struct drm_crtc_commit *commit; member
[all …]
|
| D | drm_modeset_helper_vtables.h | 100 * @commit:
102 * This callback should commit the new mode on the CRTC after a modeset,
112 void (*commit)(struct drm_crtc *crtc); member
135 * commit, and the mode validation in the probe paths it is not allowed
300 * Therefore @disable must be the inverse of @mode_set plus @commit for
328 * can add more state objects to the atomic commit if needed. Care must
367 * This hook is called before any plane commit functions are called.
372 * the tradeoffs and variants of plane commit helpers.
387 * Simple hardware or hardware with special requirements can commit and
389 * other commit hooks for plane updates.
[all …]
|
| /Linux-v6.6/drivers/interconnect/qcom/ |
| D | bcm-voter.c | 26 * @lock: mutex to protect commit and wake/sleep lists in the voter
128 u32 addr, bool commit, bool wait) in tcs_cmd_gen() argument
147 cmd->data = BCM_TCS_CMD(commit, valid, vote_x, vote_y); in tcs_cmd_gen()
162 bool commit, wait; in tcs_list_gen() local
168 commit = false; in tcs_list_gen()
172 commit = true; in tcs_list_gen()
176 wait = commit && (voter->tcs_wait & BIT(bucket)); in tcs_list_gen()
179 bcm->vote_y[bucket], bcm->addr, commit, wait); in tcs_list_gen()
186 * commit bit on the last BCM request of every VCD. in tcs_list_gen()
189 if (!commit) { in tcs_list_gen()
[all …]
|
| /Linux-v6.6/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | memory.json | 52 "BriefDescription": "Number of times HLE commit succeeded",
54 "EventName": "HLE_RETIRED.COMMIT",
55 "PublicDescription": "Number of times HLE commit succeeded.",
245 "BriefDescription": "Number of times RTM commit succeeded",
247 "EventName": "RTM_RETIRED.COMMIT",
248 "PublicDescription": "Number of times RTM commit succeeded.",
315 …"BriefDescription": "Number of times a TSX Abort was triggered due to release/commit but data and …
318 …"PublicDescription": "Number of times a TSX Abort was triggered due to release/commit but data and…
323 …"BriefDescription": "Number of times a TSX Abort was triggered due to commit but Lock Buffer not e…
326 …"PublicDescription": "Number of times a TSX Abort was triggered due to commit but Lock Buffer not …
[all …]
|
