Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright (c) 2016 The Chromium Authors. All rights reserved. | |
| 2 // Use of this source code is governed by a BSD-style license that can be | |
| 3 // found in the LICENSE file. | |
| 4 | |
| 5 #ifndef CHROME_COMMON_PREFETCH_ARGUMENT_WIN_H_ | |
| 6 #define CHROME_COMMON_PREFETCH_ARGUMENT_WIN_H_ | |
| 7 | |
| 8 namespace base { | |
| 9 class CommandLine; | |
| 10 } // namespace base | |
| 11 | |
| 12 namespace chrome { | |
| 13 // Adds a prefetch argument to |command_line|. The --type and | |
| 14 // --no-startup-window switches must already have been added, if applicable, as | |
|
gab
2016/01/18 19:10:52
I find it weird to have to document which flags ha
| |
| 15 // they determine which prefetch argument is added to |command_line|. It has | |
| 16 // been observed that when file reads are consistent for 3 process launches with | |
| 17 // the same prefetch argument, the prefetcher starts issuing the reads in batch | |
| 18 // at process launch. This is more efficient than reading a few pages at the | |
| 19 // time on-demand. The prefetcher wouldn't be able to observe consistent file | |
|
gab
2016/01/18 19:10:52
s/at the time/at a time/
gab
2016/01/18 19:10:52
s/wouldn't/isn't/
| |
| 20 // reads across Chrome process launches if no prefetch argument was used, | |
| 21 // because the reads depend on the process type. | |
| 22 void AddWindowsPrefetchArgument(base::CommandLine* command_line); | |
|
gab
2016/01/18 19:10:52
To ensure this is called by everyone creating a ch
| |
| 23 } // namespace chrome | |
| 24 | |
| 25 #endif // CHROME_COMMON_PREFETCH_ARGUMENT_WIN_H_ | |
| OLD | NEW |