AFIO  v2.00 late alpha
afio_v2_xxx::handle Class Reference

A native_handle_type which is managed by the lifetime of this object instance. More...

#include "handle.hpp"

Inheritance diagram for afio_v2_xxx::handle:
afio_v2_xxx::io_handle afio_v2_xxx::path_handle afio_v2_xxx::section_handle afio_v2_xxx::file_handle afio_v2_xxx::map_handle afio_v2_xxx::directory_handle afio_v2_xxx::async_file_handle afio_v2_xxx::mapped_file_handle

Classes

struct  flag_base
 Bitwise flags which can be specified. More...
 

Public Types

enum  mode : unsigned char {
  unchanged = 0, mode::none = 2, mode::attr_read = 4, mode::attr_write = 5,
  mode::read = 6, mode::write = 7, mode::append = 9
}
 The behaviour of the handle: does it read, read and write, or atomic append? More...
 
enum  creation : unsigned char { open_existing = 0, only_if_not_exist, if_needed, creation::truncate }
 On opening, do we also create a new file or truncate an existing one? More...
 
enum  caching : unsigned char {
  unchanged = 0, caching::none = 1, caching::only_metadata = 2, caching::reads = 3,
  caching::reads_and_metadata = 5, caching::all = 4, caching::safety_fsyncs = 7, caching::temporary = 6
}
 What i/o on the handle will complete immediately due to kernel caching. More...
 
using path_type = filesystem::path
 The path type used by this handle.
 
using extent_type = unsigned long long
 The file extent type used by this handle.
 
using size_type = size_t
 The memory extent type used by this handle.
 
using flag = quickcpplib::_xxx ::bitfield::bitfield< flag_base >
 

Public Member Functions

constexpr handle ()
 Default constructor.
 
constexpr handle (native_handle_type h, caching caching=caching::none, flag flags=flag::none) noexcept
 Construct a handle from a supplied native handle.
 
 handle (const handle &)=delete
 No copy construction (use clone())
 
handleoperator= (const handle &o)=delete
 No copy assignment.
 
constexpr handle (handle &&o) noexcept
 Move the handle.
 
handleoperator= (handle &&o) noexcept
 Move assignment of handle.
 
void swap (handle &o) noexcept
 Swap with another instance.
 
virtual result< path_typecurrent_path () const noexcept
 
virtual result< void > close () noexcept
 Immediately close the native handle type managed by this handle.
 
result< handleclone () const noexcept
 
virtual native_handle_type release () noexcept
 Release the native handle type managed by this handle.
 
bool is_valid () const noexcept
 True if the handle is valid (and usually open)
 
bool is_readable () const noexcept
 True if the handle is readable.
 
bool is_writable () const noexcept
 True if the handle is writable.
 
bool is_append_only () const noexcept
 True if the handle is append only.
 
virtual result< void > set_append_only (bool enable) noexcept
 
bool is_overlapped () const noexcept
 True if overlapped.
 
bool is_seekable () const noexcept
 True if seekable.
 
bool requires_aligned_io () const noexcept
 True if requires aligned i/o.
 
bool is_regular () const noexcept
 True if a regular file or device.
 
bool is_directory () const noexcept
 True if a directory.
 
bool is_symlink () const noexcept
 True if a symlink.
 
bool is_multiplexer () const noexcept
 True if a multiplexer like BSD kqueues, Linux epoll or Windows IOCP.
 
bool is_process () const noexcept
 True if a process.
 
bool is_section () const noexcept
 True if a memory section.
 
caching kernel_caching () const noexcept
 Kernel cache strategy used by this handle.
 
bool are_reads_from_cache () const noexcept
 True if the handle uses the kernel page cache for reads.
 
bool are_writes_durable () const noexcept
 True if writes are safely on storage on completion.
 
bool are_safety_fsyncs_issued () const noexcept
 True if issuing safety fsyncs is on.
 
flag flags () const noexcept
 The flags this handle was opened with.
 
native_handle_type native_handle () const noexcept
 The native handle used by this handle.
 

Protected Attributes

caching _caching {caching::none}
 
flag _flags {flag::none}
 
native_handle_type _v
 

Friends

class fs_handle
 
std::ostream & operator<< (std::ostream &s, const handle &v)
 

Detailed Description

A native_handle_type which is managed by the lifetime of this object instance.

Member Enumeration Documentation

◆ caching

enum afio_v2_xxx::handle::caching : unsigned char
strong

What i/o on the handle will complete immediately due to kernel caching.

Enumerator
none 

No caching whatsoever, all reads and writes come from storage (i.e. O_DIRECT|O_SYNC). Align all i/o to 4Kb boundaries for this to work. flag_disable_safety_fsyncs can be used here.

only_metadata 

Cache reads and writes of metadata but avoid caching data (O_DIRECT), thus i/o here does not affect other cached data for other handles. Align all i/o to 4Kb boundaries for this to work.

reads 

Cache reads only. Writes of data and metadata do not complete until reaching storage (O_SYNC). flag_disable_safety_fsyncs can be used here.

reads_and_metadata 

Cache reads and writes of metadata, but writes of data do not complete until reaching storage (O_DSYNC). flag_disable_safety_fsyncs can be used here.

all 

Cache reads and writes of data and metadata so they complete immediately, sending writes to storage at some point when the kernel decides (this is the default file system caching on a system).

safety_fsyncs 

Cache reads and writes of data and metadata so they complete immediately, but issue safety fsyncs at certain points. See documentation for flag_disable_safety_fsyncs.

temporary 

Cache reads and writes of data and metadata so they complete immediately, only sending any updates to storage on last handle close in the system or if memory becomes tight as this file is expected to be temporary (Windows and FreeBSD only).

83  : unsigned char // bit 0 set means safety fsyncs enabled
84  {
85  unchanged = 0,
86  none = 1, //!< No caching whatsoever, all reads and writes come from storage (i.e. <tt>O_DIRECT|O_SYNC</tt>). Align all i/o to 4Kb boundaries for this to work. <tt>flag_disable_safety_fsyncs</tt> can be used here.
87  only_metadata = 2, //!< Cache reads and writes of metadata but avoid caching data (<tt>O_DIRECT</tt>), thus i/o here does not affect other cached data for other handles. Align all i/o to 4Kb boundaries for this to work.
88  reads = 3, //!< Cache reads only. Writes of data and metadata do not complete until reaching storage (<tt>O_SYNC</tt>). <tt>flag_disable_safety_fsyncs</tt> can be used here.
89  reads_and_metadata = 5, //!< Cache reads and writes of metadata, but writes of data do not complete until reaching storage (<tt>O_DSYNC</tt>). <tt>flag_disable_safety_fsyncs</tt> can be used here.
90  all = 4, //!< Cache reads and writes of data and metadata so they complete immediately, sending writes to storage at some point when the kernel decides (this is the default file system caching on a system).
91  safety_fsyncs = 7, //!< Cache reads and writes of data and metadata so they complete immediately, but issue safety fsyncs at certain points. See documentation for <tt>flag_disable_safety_fsyncs</tt>.
92  temporary = 6 //!< Cache reads and writes of data and metadata so they complete immediately, only sending any updates to storage on last handle close in the system or if memory becomes tight as this file is expected to be temporary (Windows and FreeBSD only).
93  // NOTE: IF UPDATING THIS UPDATE THE std::ostream PRINTER BELOW!!!
94  };

◆ creation

enum afio_v2_xxx::handle::creation : unsigned char
strong

On opening, do we also create a new file or truncate an existing one?

Enumerator
truncate 

Atomically truncate on open, leaving creation date unmodified.

74  : unsigned char
75  {
76  open_existing = 0,
77  only_if_not_exist,
78  if_needed,
79  truncate //!< Atomically truncate on open, leaving creation date unmodified.
80  // NOTE: IF UPDATING THIS UPDATE THE std::ostream PRINTER BELOW!!!
81  };
result< file_handle::extent_type > truncate(file_handle &self, file_handle::extent_type newsize) noexcept
Definition: file_handle.hpp:373

◆ mode

enum afio_v2_xxx::handle::mode : unsigned char
strong

The behaviour of the handle: does it read, read and write, or atomic append?

Enumerator
none 

No ability to read or write anything, but can synchronise (SYNCHRONIZE or 0)

attr_read 

Ability to read attributes (FILE_READ_ATTRIBUTES|SYNCHRONIZE or O_RDONLY)

attr_write 

Ability to read and write attributes (FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES|SYNCHRONIZE or O_RDONLY)

read 

Ability to read (READ_CONTROL|FILE_READ_DATA|FILE_READ_ATTRIBUTES|FILE_READ_EA|SYNCHRONISE or O_RDONLY)

write 

Ability to read and write (READ_CONTROL|FILE_READ_DATA|FILE_READ_ATTRIBUTES|FILE_READ_EA|FILE_WRITE_DATA|FILE_WRITE_ATTRIBUTES|FILE_WRITE_EA|FILE_APPEND_DATA|SYNCHRONISE or O_RDWR)

append 

All mainstream OSs and CIFS guarantee this is atomic with respect to all other appenders (FILE_APPEND_DATA|SYNCHRONISE or O_APPEND)

62  : unsigned char // bit 0 set means writable
63  {
64  unchanged = 0,
65  none = 2, //!< No ability to read or write anything, but can synchronise (SYNCHRONIZE or 0)
66  attr_read = 4, //!< Ability to read attributes (FILE_READ_ATTRIBUTES|SYNCHRONIZE or O_RDONLY)
67  attr_write = 5, //!< Ability to read and write attributes (FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES|SYNCHRONIZE or O_RDONLY)
68  read = 6, //!< Ability to read (READ_CONTROL|FILE_READ_DATA|FILE_READ_ATTRIBUTES|FILE_READ_EA|SYNCHRONISE or O_RDONLY)
69  write = 7, //!< Ability to read and write (READ_CONTROL|FILE_READ_DATA|FILE_READ_ATTRIBUTES|FILE_READ_EA|FILE_WRITE_DATA|FILE_WRITE_ATTRIBUTES|FILE_WRITE_EA|FILE_APPEND_DATA|SYNCHRONISE or O_RDWR)
70  append = 9 //!< All mainstream OSs and CIFS guarantee this is atomic with respect to all other appenders (FILE_APPEND_DATA|SYNCHRONISE or O_APPEND)
71  // NOTE: IF UPDATING THIS UPDATE THE std::ostream PRINTER BELOW!!!
72  };
io_handle::io_result< io_handle::buffers_type > read(io_handle &self, io_handle::io_request< io_handle::buffers_type > reqs, deadline d=deadline()) noexcept
Read data from the open handle.
Definition: io_handle.hpp:467
io_handle::io_result< io_handle::const_buffers_type > write(io_handle &self, io_handle::io_request< io_handle::const_buffers_type > reqs, deadline d=deadline()) noexcept
Write data to the open handle.
Definition: io_handle.hpp:493

Member Function Documentation

◆ clone()

result<handle> afio_v2_xxx::handle::clone ( ) const
inlinenoexcept

Clone this handle (copy constructor is disabled to avoid accidental copying)

Errors returnable
Any of the values POSIX dup() or DuplicateHandle() can return.

◆ current_path()

virtual result<path_type> afio_v2_xxx::handle::current_path ( ) const
inlinevirtualnoexcept

Returns the current path of the open handle as said by the operating system. Note that you are NOT guaranteed that any path refreshed bears any resemblance to the original, some operating systems will return some different path which still reaches the same inode via some other route e.g. hardlinks, dereferenced symbolic links, etc. Windows and Linux correctly track changes to the specific path the handle was opened with, not getting confused by other hard links. MacOS nearly gets it right, but under some circumstances e.g. renaming may switch to a different hard link's path which is almost certainly a bug.

If AFIO was not able to determine the current path for this open handle e.g. the inode has been unlinked, it returns an empty path. Be aware that FreeBSD can return an empty (deleted) path for file inodes no longer cached by the kernel path cache, AFIO cannot detect the difference. FreeBSD will also return any path leading to the inode if it is hard linked. FreeBSD does implement path retrieval for directory inodes correctly however, and see algorithm::stablized_path<T> for a handle adapter which makes use of that.

On Linux if /proc is not mounted, this call fails with an error. All APIs in AFIO which require the use of current_path() can be told to not use it e.g. flag::disable_safety_unlinks. It is up to you to detect if current_path() is not working, and to change how you call AFIO appropriately.

Warning
This call is expensive, it always asks the kernel for the current path, and no checking is done to ensure what the kernel returns is accurate or even sensible. Be aware that despite these precautions, paths are unstable and can change randomly at any moment. Most code written to use absolute file systems paths is racy, so don't do it, use path_handle to fix a base location on the file system and work from that anchor instead!
Memory Allocations
At least one malloc for the path_type, likely several more.
See also
algorithm::cached_parent_handle_adapter<T> which overrides this with an implementation based on retrieving the current path of a cached handle to the parent directory. On platforms with instability or failure to retrieve the correct current path for regular files, the cached parent handle adapter works around the problem by taking advantage of directory inodes not having the same instability problems on any platform.

◆ set_append_only()

virtual result<void> afio_v2_xxx::handle::set_append_only ( bool  enable)
inlinevirtualnoexcept

Changes whether this handle is append only or not.

Warning
On Windows this is implemented as a bit of a hack to make it fast like on POSIX, so make sure you open the handle for read/write originally. Note unlike on POSIX the append_only disposition will be the only one toggled, seekable and readable will remain turned on.
Errors returnable
Whatever POSIX fcntl() returns. On Windows nothing is changed on the handle.
Memory Allocations
No memory allocation.

The documentation for this class was generated from the following file: