diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-26 06:07:25 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-26 06:07:25 +0000 |
| commit | 46f6e20943cf84fbde08342710dbe5b6b410bee6 (patch) | |
| tree | ec4d267c4123faeafdafe51382861563bb6140c2 /base/atomicops_internals_x86_msvc.h | |
| parent | c5a0548f3a17d7b5d01adddb7e9c11b5054a92a4 (diff) | |
| download | chromium_src-46f6e20943cf84fbde08342710dbe5b6b410bee6.zip chromium_src-46f6e20943cf84fbde08342710dbe5b6b410bee6.tar.gz chromium_src-46f6e20943cf84fbde08342710dbe5b6b410bee6.tar.bz2 | |
Revert 40099 - Revert 39998 Revert 39996 Refine IPv6 probe to require that the client has an IPv6 address on an interface
It is indeed causing a perf regression in startup on Linux...
I'll need to rearchitect to do the probes asynchronously, and get
off the startup-critical-path.
This currently only works on Posix, not windows.
Network changes are monitored, and the test is repeated each time interfaces
change (which is a subset of any IP addresses changing).
The test performed is still relatively low latency, and we *may* need
to eventually move to an high latency test, such as a DNS resolution,
or an actual test connection. If we move in that direction, then we'll
need to post a task to perform the work, rather than immediately returning.
BUG=25680
BUG=12754
r=wtc,eroman
Review URL: http://codereview.chromium.org/652072
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/660073
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/661164
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/660165
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40101 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/atomicops_internals_x86_msvc.h')
0 files changed, 0 insertions, 0 deletions