Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
5965b642
Commit
5965b642
authored
Sep 04, 2014
by
NeilBrown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
md/raid1: minor typos and reformatting.
Signed-off-by:
NeilBrown
<
neilb@suse.de
>
parent
4b5060dd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
drivers/md/raid1.c
drivers/md/raid1.c
+7
-7
No files found.
drivers/md/raid1.c
View file @
5965b642
...
...
@@ -901,18 +901,18 @@ static sector_t wait_barrier(struct r1conf *conf, struct bio *bio)
* However if there are already pending
* requests (preventing the barrier from
* rising completely), and the
* p
re
-process bio queue isn't empty,
* p
er
-process bio queue isn't empty,
* then don't wait, as we need to empty
* that queue to
get the nr_pending
*
count down
.
* that queue to
allow conf->start_next_window
*
to increase
.
*/
wait_event_lock_irq
(
conf
->
wait_barrier
,
!
conf
->
array_frozen
&&
(
!
conf
->
barrier
||
((
conf
->
start_next_window
<
conf
->
next_resync
+
RESYNC_SECTORS
)
&&
current
->
bio_list
&&
!
bio_list_empty
(
current
->
bio_list
))),
((
conf
->
start_next_window
<
conf
->
next_resync
+
RESYNC_SECTORS
)
&&
current
->
bio_list
&&
!
bio_list_empty
(
current
->
bio_list
))),
conf
->
resync_lock
);
conf
->
nr_waiting
--
;
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment