Ticket #21 (new feature)

Opened 21 months ago

Last modified 13 months ago

remount thread adds complexity to pvfs2-client build

Reported by: carns Owned by: carns
Priority: trivial Component: Client Daemon
Version: HEAD Keywords: remount thread pvfs2-client-core
Cc:

Description

pvfs2-client-core uses one special purpose thread to handle certain remount situations. It is not active for most of the pvfs2-client-core runtime. However, its presence means that libpthread must always be linked in and gen_mutex locking must be enabled.

If it isn't too invasive, it might be nice to find a way to eliminate this remount thread.

Change History

Changed 13 months ago by carns

A better first step would be to build the library used by pvfs2-client with thread safety disabled (as in the --disable-thread-safety) configuration option. This is a significant performance improvement on the BG/P I/O nodes and doesn't impact correctness in any way.

Do we just switch to disable thread safety for the library as a whole by default? Or do we build a seperate library just for pvfs2-client?

Note: See TracTickets for help on using tickets.