from small one page howto to huge articles all in one place
 

search text in:





Poll
Which filesystem do you use?






poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

91113

userrating:

average rating: 1.7 (82 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

206972

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

88523

userrating:

average rating: 1.3 (28 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





io_prep_fsync

Section: Linux (3)
Updated: 2002-09-12
Index Return to Main Contents
 

NAME

io_prep_fsync - Synchronize a file's complete in-core state with that on disk  

SYNOPSYS

#include <errno.h>

#include <libaio.h>
static inline void io_prep_fsync(struct iocb *iocb, int fd) struct iocb { void *data; unsigned key; short aio_lio_opcode; short aio_reqprio; int aio_fildes; };
 

DESCRIPTION

This is an inline convenience function for setting up an iocbv for a FSYNC request.
The file for which
iocb->aio_fildes = fd
is a descriptor is set up with the command
iocb->aio_lio_opcode = IO_CMD_FSYNC:

The io_prep_fsync() function shall set up an IO_CMD_FSYNC operation to asynchronously force all I/O operations associated with the file indicated by the file descriptor aio_fildes member of the iocb structure referenced by the iocb argument and queued at the time of the call to io_submit() to the synchronized I/O completion state. The function call shall return when the synchronization request has been initiated or queued to the file or device (even when the data cannot be synchronized immediately).

All currently queued I/O operations shall be completed as if by a call to fsync(); that is, as defined for synchronized I/O file integrity completion. If the operation queued by io_prep_fsync() fails, then, as for fsync(), outstanding I/O operations are not guaranteed to have been completed.

If io_prep_fsync() succeeds, then it is only the I/O that was queued at the time of the call to io_submit() that is guaranteed to be forced to the relevant completion state. The completion of subsequent I/O on the file descriptor is not guaranteed to be completed in a synchronized fashion.

This function returns immediately . To schedule the operation, the function io_submit must be called.

Simultaneous asynchronous operations using the same iocb produce undefined results.  

RETURN VALUES

None  

ERRORS

None  

SEE ALSO

io(3), io_cancel(3), io_fsync(3), io_getevents(3), io_prep_pread(3), io_prep_pwrite(3), io_queue_init(3), io_queue_release(3), io_queue_run(3), io_queue_wait(3), io_set_callback(3), io_submit(3), errno(3)


 

Index

NAME
SYNOPSYS
DESCRIPTION
RETURN VALUES
ERRORS
SEE ALSO


Please read "Why adblockers are bad".



Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2013 Sascha Nitsch Unternehmensberatung UG(haftungsbeschränkt)
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 4.7 ms