The OS will already page out your stacks/process after some time of inactivity. I believe a thread becomes a candidate after about 4 seconds. Once the pages become a candidate for theft, then it's only a matter of time and memory pressure when the Memory Manager will rip them away and use them for something else.
Basically, you don't need to give a 'hint' to the OS since it will do what you want on its own. On the other hand, if you want the thread to run quickly when it gets signaled, you may be in trouble because of this behavior. If the pages make it to the disk, it could take about 10-15 milliseconds between when your thread is activated and when it can run (this is the typical seek time of a laptop disk). If the disk is already busy, it could take even longer.