[BACK]Return to rf_dagflags.h CVS log [TXT][DIR] Up to [local] / sys / dev / raidframe

File: [local] / sys / dev / raidframe / rf_dagflags.h (download)

Revision 1.1, Tue Mar 4 16:09:45 2008 UTC (16 years, 2 months ago) by nbrk
Branch point for: MAIN

Initial revision

/*	$OpenBSD: rf_dagflags.h,v 1.3 2002/12/16 07:01:03 tdeval Exp $	*/
/*	$NetBSD: rf_dagflags.h,v 1.3 1999/02/05 00:06:08 oster Exp $	*/

/*
 * Copyright (c) 1995 Carnegie-Mellon University.
 * All rights reserved.
 *
 * Author: Mark Holland
 *
 * Permission to use, copy, modify and distribute this software and
 * its documentation is hereby granted, provided that both the copyright
 * notice and this permission notice appear in all copies of the
 * software, derivative works or modified versions, and any portions
 * thereof, and that both notices appear in supporting documentation.
 *
 * CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
 * CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND
 * FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
 *
 * Carnegie Mellon requests users of this software to return to
 *
 *  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
 *  School of Computer Science
 *  Carnegie Mellon University
 *  Pittsburgh PA 15213-3890
 *
 * any improvements or extensions that they make and grant Carnegie the
 * rights to redistribute these changes.
 */

/*****************************************************************************
 *
 * dagflags.h -- Flags that can be given to DoAccess.
 * I pulled these out of dag.h because routines that call DoAccess may need
 * these flags, but certainly do not need the declarations related to the DAG
 * data structures.
 *
 *****************************************************************************/


#ifndef	_RF__RF_DAGFLAGS_H_
#define	_RF__RF_DAGFLAGS_H_

/*
 * Bitmasks for the "flags" parameter (RF_RaidAccessFlags_t) used
 * by DoAccess, SelectAlgorithm, and the DAG creation routines.
 *
 * If USE_DAG or USE_ASM is specified, neither the DAG nor the ASM
 * will be modified, which means that you can't SUPRESS if you
 * specify USE_DAG.
 */

#define	RF_DAG_FLAGS_NONE		    0	/* No flags */
#define	RF_DAG_SUPPRESS_LOCKS		(1<<0)	/*
						 * Supress all stripe locks in
						 * the DAG.
						 */
#define	RF_DAG_RETURN_ASM		(1<<1)	/*
						 * Create an ASM and return it
						 * instead of freeing it.
						 */
#define	RF_DAG_RETURN_DAG		(1<<2)	/*
						 * Create a DAG and return it
						 * instead of freeing it.
						 */
#define	RF_DAG_NONBLOCKING_IO		(1<<3)	/*
						 * Cause DoAccess to be
						 * non-blocking.
						 */
#define	RF_DAG_ACCESS_COMPLETE		(1<<4)	/*
						 * The access is complete.
						 */
#define	RF_DAG_DISPATCH_RETURNED	(1<<5)	/*
						 * Used to handle the case
						 * where the dag invokes no
						 * I/O.
						 */
#define	RF_DAG_TEST_ACCESS		(1<<6)	/*
						 * This access came through
						 * rf_ioctl instead of
						 * rf_strategy.
						 */

#endif	/* !_RF__RF_DAGFLAGS_H_ */