blob: 19c19ffcf1d05d1d988a4c6172ff507c05a811c0 (
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
|
/*
* Copyright 2015 Google Inc.
*
* Use of this source code is governed by a BSD-style license that can be
* found in the LICENSE file.
*/
#include "GrBatch.h"
#include "GrMemoryPool.h"
#include "SkSpinlock.h"
// TODO I noticed a small benefit to using a larger exclusive pool for batches. Its very small,
// but seems to be mostly consistent. There is a lot in flux right now, but we should really
// revisit this when batch is everywhere
// We use a global pool protected by a mutex(spinlock). Chrome may use the same GrContext on
// different threads. The GrContext is not used concurrently on different threads and there is a
// memory barrier between accesses of a context on different threads. Also, there may be multiple
// GrContexts and those contexts may be in use concurrently on different threads.
namespace {
SK_DECLARE_STATIC_SPINLOCK(gBatchSpinlock);
class MemoryPoolAccessor {
public:
MemoryPoolAccessor() { gBatchSpinlock.acquire(); }
~MemoryPoolAccessor() { gBatchSpinlock.release(); }
GrMemoryPool* pool() const {
static GrMemoryPool gPool(16384, 16384);
return &gPool;
}
};
}
int32_t GrBatch::gCurrBatchClassID = GrBatch::kIllegalBatchID;
GrBATCH_SPEW(int32_t GrBatch::gCurrBatchUniqueID = GrBatch::kIllegalBatchID;)
void* GrBatch::operator new(size_t size) {
return MemoryPoolAccessor().pool()->allocate(size);
}
void GrBatch::operator delete(void* target) {
return MemoryPoolAccessor().pool()->release(target);
}
GrBatch::GrBatch(uint32_t classID)
: fClassID(classID)
#if GR_BATCH_SPEW
, fUniqueID(GenBatchID())
#endif
{
SkDEBUGCODE(fUsed = false;)
}
GrBatch::~GrBatch() {}
|
