Sponsored Content
Operating Systems Linux Is Concurrent I/O (CIO) available on Linux? Post 302405451 by jim mcnamara on Friday 19th of March 2010 12:10:52 AM
Old 03-19-2010
No, there is nothing that exactly matches concurrent I/O. AFAIK. You can back into it by turning off file caching, for example:

You can drop_caches for a one-time flush:

Writing to this will cause the kernel to drop clean caches, dentries and
inodes from memory, causing that memory to become free.
Code:
To free pagecache:
	echo 1 > /proc/sys/vm/drop_caches
To free dentries and inodes:
	echo 2 > /proc/sys/vm/drop_caches
To free pagecache, dentries and inodes:
	echo 3 > /proc/sys/vm/drop_caches

This is a non-destructive operation and dirty data objects are not freeable, the
user should run `sync' first.

You can mount filesystems
Code:
 mount -o sync ....

to bypass file caching
The dirsync flag also bypasses file metadata update caching. Doing these can increase your exposure to possible data loss for long term operation.

You can use the O_DIRECT flag on open.

If this question refers to a db applications I would bet the system designers are aware of all of this for a linux install. Are you experiencing performance issues?
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

turning CIO on and how to monitor

Hi Guys, I have a database server where we run AIX 5.3 on a power5 box and we just turned on CIO (concurrent I/O) for the database filesystems. Now my assumption is that enabling CIO the database basically will bypass the filesystem cache releasing some extra memory that can be allocated... (1 Reply)
Discussion started by: hariza
1 Replies

2. AIX

turning CIO on and how to monitor

Hi Guys, I have a database server where we run AIX 5.3 on a power5 box and we just turned on CIO (concurrent I/O) for the database filesystems. Now my assumption is that enabling CIO the database basically will bypass the filesystem cache releasing some extra memory that can be allocated... (1 Reply)
Discussion started by: hariza
1 Replies

3. UNIX for Advanced & Expert Users

CIO in AIX

Hi, I'm reading AIX documentation : Examples 1.To list the mounted file systems, enter: mountThis command produces output similar to the following: node mounted mounted over vfs date options ---- ------- ------------ --- ------------ ... (2 Replies)
Discussion started by: big123456
2 Replies

4. AIX

Difference between concurrent and enhanced concurrent VG

Hi, What are the differences between concurrent and enhanced concurrent VGs.? Any advantages of enhanced concurrent VG over normal concurrent vg Regards, Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies
SYNC(8) 						     Linux Programmer's Manual							   SYNC(8)

NAME
sync - synchronize data on disk with memory SYNOPSIS
sync [--help] [--version] DESCRIPTION
sync writes any data buffered in memory out to disk. This can include (but is not limited to) modified superblocks, modified inodes, and delayed reads and writes. This must be implemented by the kernel; The sync program does nothing but exercise the sync(2) system call. The kernel keeps data in memory to avoid doing (relatively slow) disk reads and writes. This improves performance, but if the computer crashes, data may be lost or the file system corrupted as a result. sync ensures that everything in memory is written to disk. sync should be called before the processor is halted in an unusual manner (e.g., before causing a kernel panic when debugging new kernel code). In general, the processor should be halted using the shutdown(8) or reboot(8) or halt(8) commands, which will attempt to put the system in a quiescent state before calling sync(2). (Various implementations of these commands exist; consult your documentation; on some systems one should not call reboot(8) and halt(8) directly.) OPTIONS
--help Print a usage message on standard output and exit successfully. --version Print version information on standard output, then exit successfully. -- Terminate option list. ENVIRONMENT
The variables LANG, LC_ALL, LC_CTYPE, and LC_MESSAGES have the usual meaning. CONFORMING TO
POSIX.2. NOTES
On Linux, sync is only guaranteed to schedule the dirty blocks for writing; it can actually take a short time before all the blocks are finally written. The reboot(8) and halt(8) commands take this into account by sleeping for a few seconds after calling sync(2). This page describes sync as found in the fileutils-4.0 package; other versions may differ slightly. SEE ALSO
sync(2), halt(8), reboot(8), update(8) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
1998-11-01 SYNC(8)
All times are GMT -4. The time now is 03:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy