1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
/* $OpenBSD: rf_archs.h,v 1.2 1999/02/16 00:02:23 niklas Exp $ */
/* $NetBSD: rf_archs.h,v 1.4 1999/02/05 00:06:06 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.
*/
/* rf_archs.h -- defines for which architectures you want to
* include is some particular build of raidframe. Unfortunately,
* it's difficult to exclude declustering, P+Q, and distributed
* sparing because the code is intermixed with RAID5 code. This
* should be fixed.
*
* this is really intended only for use in the kernel, where I
* am worried about the size of the object module. At user level and
* in the simulator, I don't really care that much, so all the
* architectures can be compiled together. Note that by itself, turning
* off these defines does not affect the size of the executable; you
* have to edit the makefile for that.
*
* comment out any line below to eliminate that architecture.
* the list below includes all the modules that can be compiled
* out.
*
*/
#ifndef _RF__RF_ARCHS_H_
#define _RF__RF_ARCHS_H_
/*
* Turn off if you do not have CMU PDL support compiled
* into your kernel.
*/
#ifndef RF_CMU_PDL
#define RF_CMU_PDL 0
#endif /* !RF_CMU_PDL */
/*
* Khalil's performance-displaying demo stuff.
* Relies on CMU meter tools.
*/
#define RF_INCLUDE_EVENODD 1
#define RF_INCLUDE_RAID5_RS 1
#define RF_INCLUDE_PARITYLOGGING 1
#define RF_INCLUDE_CHAINDECLUSTER 1
#define RF_INCLUDE_INTERDECLUSTER 1
#define RF_INCLUDE_RAID0 1
#define RF_INCLUDE_RAID1 1
#define RF_INCLUDE_RAID4 1
#define RF_INCLUDE_RAID5 1
#define RF_INCLUDE_RAID6 0
#define RF_INCLUDE_DECL_PQ 0
#define RF_MEMORY_REDZONES 0
#define RF_RECON_STATS 1
#define RF_INCLUDE_QUEUE_RANDOM 0
#define RF_KEEP_DISKSTATS 1
/* These two symbols enable nonstandard forms of error recovery.
* These modes are only valid for performance measurements and
* data corruption will occur if an error occurs when either
* forward or backward error recovery are enabled. In general
* both of the following two definitions should be commented
* out--this forces RAIDframe to use roll-away error recovery
* which does guarantee proper error recovery without data corruption
*/
/* #define RF_FORWARD 1 */
/* #define RF_BACKWARD 1 */
#include "rf_options.h"
#endif /* !_RF__RF_ARCHS_H_ */
|
