add settings_for_path() utility function

[arvidn]

to optimize disk I/O settings based on the save path. This patch looks at these properties of the drive of the specified path:

1. Is it a spinning disk or SSD (windows boils this down to, is there a penalty to seek)
2. If it's an SSD, is it DAX? (which is really where memory mapped files would shine)
3. Is it a network share (where memory mapped files probably won't to so well)

This is still work in progress and I'm interested in feedback.

• [ ] python binding
• [ ] consider feasibility to also hint on what disk I/O back-end to use
• [ ] consider feasibility to also provide per-torrent settings

[glassez]

@arvidn IIRC, you want to determine drive types and use different disk IO backends for different drives?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.