Reimplement Exercise 4.11 to use multiple threads. Because the current working directory is a process attribute, it is shared by all threads, so you can’t use chdir(2). Instead, use the *at functions to allow 16 worker threads to process different parts of the ?le system at the same time. How much faster is this version compared to the version from Exercise 4.11?

What will be an ideal response?

Because the user-de?ned function passed to ftw is passed a full pathname, we must maintain the absolute pathname, so we really don’t need to use any *at functions. But that would be no fun, so we’ll use fstatat(2) instead oflstat(2). With multiple threads, we need to protect the data structures that the threads access. Weuse a mutex to protect the list of directories to scan, and a condition variable for the threads to wait for work. We also use a spin lock to protect the counters we keep for the ?le types we encounter.The main thread starts things offand then waits for the worker threads to complete. The solution is shown in Figure33. When comparing its performance to that of the program from Exercise 4.11, you should ?nd that Exercise 4.11runs in less user time and less system time, but with moreelapsed (clock) time.