block device snapshot capability

Hello all, Is anyone aware of ongoing development to provide the capability to take a snapshot of a block device? Thanks, Jonathan -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503-578-3385 - To unsubscribe from this list: send the line "unsubscribe

block device snapshot capability

Hello all, Is anyone aware of ongoing development to provide the capability to take a snapshot of a block device? Thanks, Jonathan -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503-578-3385 - To unsubscribe from this list: send the line "unsubscribe

Re: kernel lock contention and scalability

> Tridge and I tried out the postgresql benchmark you used here and this > contention is due to a bug in postgres. From a quick strace, we found > the threads do a load of select(0, NULL, NULL, NULL, {0,0}). Basically all > threads are pounding on schedule(). ... > Our guess is that the app has

Re: kernel lock contention and scalability

Tridge and I tried out the postgresql benchmark you used here and this contention is due to a bug in postgres. From a quick strace, we found the threads do a load of select(0, NULL, NULL, NULL, {0,0}). Basically all threads are pounding on schedule(). ... Our guess is that the app has some

Re: kernel lock contention and scalability

ached 2 changes that might reduce the contention, but it's just > an idea, completely untested. Thanks for the insight into the sempahore subsystem and the suggested fixes. -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503-578-3385 - To unsubscribe from this li

Re: kernel lock contention and scalability

, but it's just an idea, completely untested. Thanks for the insight into the sempahore subsystem and the suggested fixes. -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503-578-3385 - To unsubscribe from this list: send the line "unsubscribe linux-k

kernel lock contention and scalability

regarding previous or ongoing lock contention work would be appreciated. I'm aware of timer scalability work ongoing at people.redhat.com/mingo/scalable-timers, but is anyone working on reducing sem_ids contention? -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503

kernel lock contention and scalability

regarding previous or ongoing lock contention work would be appreciated. I'm aware of timer scalability work ongoing at people.redhat.com/mingo/scalable-timers, but is anyone working on reducing sem_ids contention? -- Jonathan Lahr IBM Linux Technology Center Beaverton, Oregon [EMAIL PROTECTED] 503