接下来验证几个场景下的线程执行逻辑:
- 同一个client的多个线程调用service的同一个同步接口, 在service中这些调用会串行化吗?
- 同一个client的单个线程多次调用service的同一个同步接口,在service中这些调用会串行化吗?
- 不同的client,调用service的同一个同步接口,在service中这些调用会串行化吗?
- 同一个client的多个线程调用service的同一个异步接口, 在service中这些调用会串行化吗?
- 同一个client的单个线程多次调用service的同一个异步接口,在service中这些调用会串行化吗?
- 不同的client,调用service的同一个异步接口,在service中这些调用会串行化吗?
- 如何实现service执行各个方法串行化
同一个client的多个线程调用service的同一个同步接口, 在service中这些调用会串行化吗?
#include <aidl/android/hardware/learnHA/ILearnHA.h>
#include <android/binder_manager.h>
#include <android-base/logging.h>
#include <thread>
using aidl::android::hardware::learnHA::ILearnHA;
int main() {
std::string instance = std::string() + ILearnHA::descriptor + "/default";
LOG(INFO) << "Trying to connect to " << instance;
ndk::SpAIBinder binder(AServiceManager_checkService(instance.c_str()));
if (binder.get() == nullptr) {
LOG(ERROR) << "Service not found: " << instance;
return 1;
}
auto service = ILearnHA::fromBinder(binder);
if (!service) {
LOG(ERROR) << "fromBinder failed";
return 1;
}
std::thread t1 {
[service] {
LOG(ERROR) << "Thread 1 start ";
service->justTest();
LOG(ERROR) << "Thread 1 end ";
}
};
std::thread t2 {
[service] {
LOG(ERROR) << "Thread 2 start ";
service->justTest();
LOG(ERROR) << "Thread 2 end ";
}
};
std::thread t3 {
[service] {
LOG(ERROR) << "Thread 3 start ";
service->justTest();
LOG(ERROR) << "Thread 3 end ";
}
};
std::thread t4 {
[service] {
LOG(ERROR) << "Thread 4 start ";
service->justTest();
LOG(ERROR) << "Thread 4 end ";
}
};
std::thread t5 {
[service] {
LOG(ERROR) << "Thread 5 start ";
service->justTest();
LOG(ERROR) << "Thread 5 end ";
}
};
t1.join();
t2.join();
t3.join();
t4.join();
t5.join();
auto ret = service->justTest();
if (!ret.isOk()) {
LOG(ERROR) << "justTest failed: " << ret.getDescription();
return 1;
}
LOG(INFO) << "justTest success";
return 0;
}
client.cpp
#include "LearnHA.h"
#include <android-base/logging.h>
#include <thread>
namespace aidl {
namespace android {
namespace hardware {
namespace learnHA {
::ndk::ScopedAStatus LearnHA::justTest() {
LOG(ERROR) << "LearnHA setting enter";
LOG(ERROR) << "sleep 2s, thread id: " << std::this_thread::get_id();
std::this_thread::sleep_for(std::chrono::seconds(2));
LOG(ERROR) << "wake up, thread id: " << std::this_thread::get_id();
return ndk::ScopedAStatus::ok();
}
} // namespace light
} // namespace hardware
} // namespace android
} // namespace aidl
LearnHA.cpp
13178 13178 E android.hardware.learnHA-service: LearnHA main start
13403 13403 I android.hardware.learnHA-client: Trying to connect to android.hardware.learnHA.ILearnHA/default
13403 13404 E android.hardware.learnHA-client: Thread 1 start 473976618176
13403 13405 E android.hardware.learnHA-client: Thread 2 start 473975577792
13403 13407 E android.hardware.learnHA-client: Thread 4 start 473956719808
13403 13406 E android.hardware.learnHA-client: Thread 3 start 473957760192
13403 13408 E android.hardware.learnHA-client: Thread 5 start 473938902208
13178 13178 E android.hardware.learnHA-service: LearnHA setting enter
13178 13178 E android.hardware.learnHA-service: sleep 2s, thread id: 525914232056
13178 13179 E android.hardware.learnHA-service: LearnHA setting enter
13178 13179 E android.hardware.learnHA-service: sleep 2s, thread id: 513267268800
13178 13180 E android.hardware.learnHA-service: LearnHA setting enter
13178 13180 E android.hardware.learnHA-service: sleep 2s, thread id: 513249451200
13178 13409 E android.hardware.learnHA-service: LearnHA setting enter
13178 13409 E android.hardware.learnHA-service: sleep 2s, thread id: 513231633600
13178 13410 E android.hardware.learnHA-service: LearnHA setting enter
13178 13410 E android.hardware.learnHA-service: sleep 2s, thread id: 513213816000
13178 13180 E android.hardware.learnHA-service: wake up, thread id: 513249451200
13178 13179 E android.hardware.learnHA-service: wake up, thread id: 513267268800
13178 13178 E android.hardware.learnHA-service: wake up, thread id: 525914232056
13178 13409 E android.hardware.learnHA-service: wake up, thread id: 513231633600
13178 13410 E android.hardware.learnHA-service: wake up, thread id: 513213816000
13403 13405 E android.hardware.learnHA-client: Thread 2 end 473975577792
13403 13404 E android.hardware.learnHA-client: Thread 1 end 473976618176
13403 13406 E android.hardware.learnHA-client: Thread 3 end 473957760192
13403 13408 E android.hardware.learnHA-client: Thread 5 end 473938902208
13403 13407 E android.hardware.learnHA-client: Thread 4 end 473956719808
13178 13410 E android.hardware.learnHA-service: LearnHA setting enter
13178 13410 E android.hardware.learnHA-service: sleep 2s, thread id: 513213816000
13178 13410 E android.hardware.learnHA-service: wake up, thread id: 513213816000
13403 13403 I android.hardware.learnHA-client: justTest success
同一个 client 的多个线程,同时调用 service 的同一个同步 AIDL 接口,在 service 端不一定会串行化。
当 service 端 Binder 线程池真正启动并且有多个处理线程时,这些调用会并发执行。
同一个client的单个线程多次调用service的同一个同步接口,在service中这些调用会串行化吗?
#include <aidl/android/hardware/learnHA/ILearnHA.h>
#include <android/binder_manager.h>
#include <android-base/logging.h>
using aidl::android::hardware::learnHA::ILearnHA;
int main() {
std::string instance = std::string() + ILearnHA::descriptor + "/default";
LOG(INFO) << "Trying to connect to " << instance;
ndk::SpAIBinder binder(AServiceManager_checkService(instance.c_str()));
if (binder.get() == nullptr) {
LOG(ERROR) << "Service not found: " << instance;
return 1;
}
auto service = ILearnHA::fromBinder(binder);
if (!service) {
LOG(ERROR) << "fromBinder failed";
return 1;
}
auto ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
ret = service->justTest();
if (!ret.isOk()) {
LOG(ERROR) << "justTest failed: " << ret.getDescription();
return 1;
}
LOG(INFO) << "justTest success";
return 0;
}
client.cpp
#include "LearnHA.h"
#
432



被折叠的 条评论
为什么被折叠?



