blob: 344a85d85d882e36fa0e2a3680a1c5bd2681bd58 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
// @file dur_writetodatafiles.cpp apply the writes back to the non-private MMF after they are for certain in redo log
/**
* Copyright (C) 2009 10gen Inc.
*
* This program is free software: you can redistribute it and/or modify
* it under the terms of the GNU Affero General Public License, version 3,
* as published by the Free Software Foundation.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Affero General Public License for more details.
*
* You should have received a copy of the GNU Affero General Public License
* along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
#include "pch.h"
#include "dur_commitjob.h"
#include "dur_stats.h"
namespace mongo {
namespace dur {
void debugValidateMapsMatch();
/** apply the writes back to the non-private MMF after they are for certain in redo log
(1) todo we don't need to write back everything every group commit. we MUST write back
that which is going to be a remapped on its private view - but that might not be all
views.
(2) todo should we do this using N threads? would be quite easy
see Hackenberg paper table 5 and 6. 2 threads might be a good balance.
(3) with enough work, we could do this outside the read lock. it's a bit tricky though.
- we couldn't do it from the private views then as they may be changing. would have to then
be from the journal alignedbuffer.
- we need to be careful the file isn't unmapped on us -- perhaps a mutex or something
with MongoMMF on closes or something to coordinate that.
locking: in read lock when called
@see https://docs.google.com/drawings/edit?id=1TklsmZzm7ohIZkwgeK6rMvsdaR13KjtJYMsfLr175Zc&hl=en
*/
void WRITETODATAFILES() {
/* we go backwards as what is at the end is most likely in the cpu cache. it won't be much, but we'll take it. */
for( set<WriteIntent>::const_iterator it(commitJob.writes().begin()), end(commitJob.writes().end()); it != end; ++it ){
const WriteIntent& intent = *it;
stats.curr._writeToDataFilesBytes += intent.length();
dassert(intent.w_ptr);
memcpy(intent.w_ptr, intent.start(), intent.length());
}
debugValidateMapsMatch();
}
}
}
|
