Rooba
/
boinc
mirror of https://github.com/BOINC/boinc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
boinc/lib/proc_control.h

41 lines
1.3 KiB
C
Raw Normal View History

- more code shuffling: proc_control: controlling processes procinfo: enumerating and querying processes run_app_windows: launching apps as other users on Win svn path=/trunk/boinc/; revision=24120
2011-09-02 18:23:13 +00:00
// This file is part of BOINC.
// http://boinc.berkeley.edu
// Copyright (C) 2011 University of California
//
// BOINC is free software; you can redistribute it and/or modify it
// under the terms of the GNU Lesser General Public License
// as published by the Free Software Foundation,
// either version 3 of the License, or (at your option) any later version.
//
// BOINC 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 Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with BOINC. If not, see <http://www.gnu.org/licenses/>.
#ifndef _PROC_CONTROL_
#define _PROC_CONTROL_
#include <vector>
- API: compile fixes for MinGW. From Oliver Bock. svn path=/trunk/boinc/; revision=24474
2011-10-24 23:38:19 +00:00
#ifdef _WIN32
#include <windows.h>
#endif
- more code shuffling: proc_control: controlling processes procinfo: enumerating and querying processes run_app_windows: launching apps as other users on Win svn path=/trunk/boinc/; revision=24120
2011-09-02 18:23:13 +00:00
extern void get_descendants(int pid, std::vector<int>& pids);
extern bool any_process_exists(std::vector<int>& pids);
extern void kill_all(std::vector<int>& pids);
#ifdef _WIN32
extern void kill_descendants();
David 11 Dec 2012 - Win process control (affects API and wrapper): Since Win doesn't have an API for process suspend/resume, we were suspending processes by 1) enumerating all the threads in the system (typically several thousand) 2) suspending those belonging to the given process The problem: for each thread, the code was calling a function in diagnostics_win.cpp to see if the thread was exempted from suspension. This check (which is unnecessary anyway if we're suspending another process) was surrounded by a semaphore acquire/release. The result: performance problems. It could take a minute to suspend the threads. Solution: 1) do the check for exemption only if we're suspending threads in our own process (i.e. from the API) 2) if we're suspending multiple processes, enumerate the threads only once, and see if each one belongs to any of the processes 3) have the wrapper elevate itself to normal priority. Otherwise it can get preempted for long periods, sometimes in the middle of scanning the threads. Note: post-9x versions of Win have a process group API that includes suspend/resume. We'll switch to this soon.
2012-12-12 00:05:40 +00:00
extern int suspend_or_resume_threads(
std::vector<int> pids, DWORD threadid, bool resume, bool check_exempt
);
- more code shuffling: proc_control: controlling processes procinfo: enumerating and querying processes run_app_windows: launching apps as other users on Win svn path=/trunk/boinc/; revision=24120
2011-09-02 18:23:13 +00:00
#else
extern void kill_descendants(int child_pid=0);
#endif
David 11 Dec 2012 - Win process control (affects API and wrapper): Since Win doesn't have an API for process suspend/resume, we were suspending processes by 1) enumerating all the threads in the system (typically several thousand) 2) suspending those belonging to the given process The problem: for each thread, the code was calling a function in diagnostics_win.cpp to see if the thread was exempted from suspension. This check (which is unnecessary anyway if we're suspending another process) was surrounded by a semaphore acquire/release. The result: performance problems. It could take a minute to suspend the threads. Solution: 1) do the check for exemption only if we're suspending threads in our own process (i.e. from the API) 2) if we're suspending multiple processes, enumerate the threads only once, and see if each one belongs to any of the processes 3) have the wrapper elevate itself to normal priority. Otherwise it can get preempted for long periods, sometimes in the middle of scanning the threads. Note: post-9x versions of Win have a process group API that includes suspend/resume. We'll switch to this soon.
2012-12-12 00:05:40 +00:00
extern void suspend_or_resume_descendants(bool resume);
- more code shuffling: proc_control: controlling processes procinfo: enumerating and querying processes run_app_windows: launching apps as other users on Win svn path=/trunk/boinc/; revision=24120
2011-09-02 18:23:13 +00:00
extern void suspend_or_resume_process(int pid, bool resume);
#endif