import of old now defunct presentation slides svn repo

3 files changed, 148 insertions, 0 deletions

diff --git a/2005/flow-accounting-ols2005/OLS2005/bottomley/Makefile.inc b/2005/flow-accounting-ols2005/OLS2005/bottomley/Makefile.inc
new file mode 100644
index 0000000..09f8079
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/bottomley/Makefile.inc
@@ -0,0 +1,7 @@
+PAPERS += bottomley/bottomley.dvi
+
+## Add any additional .tex or .eps files below:
+bottomley/bottomley.dvi bottomley/bottomley-proc.dvi: \
+	bottomley/bottomley.tex \
+	bottomley/bottomley-abstract.tex
+
diff --git a/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley-abstract.tex b/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley-abstract.tex
new file mode 100644
index 0000000..2387025
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley-abstract.tex
@@ -0,0 +1,41 @@
+
+%     Registration       Block Devices and Transport Classes: Where are we    
+%                                             going?                          
+%  Proposal           James Bottomley (jejb@steeleye.com)                     
+                                                        
+A transport class is quite simply a device driver       
+helper library with an associated sysfs component.      
+Although this sounds deceptively simple, in practise it 
+allows fairly large simplifications in device driver    
+code. Up until recently, transport classes were         
+restricted to be SCSI only, but now they can be made to 
+apply to any device driver at all (including ones with  
+no actual transports).                                  
+                                                        
+The need for a transport class comes into most device   
+driver subsystems that drive a class of devices. SCSI   
+is a really good example of this: We have a core set of 
+APIs which are needed by every SCSI driver (whether     
+Parallel SCSI, Fibre Channel or something even more     
+exotic) to do with queueing commands and interpreting   
+status codes. However, there were a large number of     
+ancillary services which don't apply to the whole of    
+SCSI, like Domain Validation for Parallel SCSI or       
+target disconnection/reconnection for Fibre Channel.    
+The sysfs exposure gives the user a well known way to   
+control device parameters (like period and offset, for  
+parallel SCSI) without having to develop a core SCSI    
+API. Since a transport class has only a sysfs interface 
+and a driver API, it is completely independent of the   
+SCSI core. This makes the classes arbitrarily           
+extensible and imposes no limit on how many may be      
+simultaneously present.                                 
+                                                        
+This talk will examine the evolution of the transport   
+class in SCSI, covering its current uses in Parallel   
+SCSI (SPI), Fibre Channel (FC) and other transports     
+(iSCSI and SAS), contrasting it with previous           
+approaches, like CAM, and follow with a description of  
+how the concept was freed from the SCSI subsystem and   
+how it could be applied in other aspects of kernel      
+development, particularly block devices.                
diff --git a/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley.tex b/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley.tex
new file mode 100644
index 0000000..4fe8da4
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/bottomley/bottomley.tex
@@ -0,0 +1,100 @@
+% The file must begin with this \documentclass declaration. You can 
+% give one of three different options which control how picky LaTeX 
+% is when typesetting:
+%
+% galley - All ``this doesn't fit'' warnings are suppressed, and 
+%          references are disabled (the key will be printed as a
+%          reminder).  Use this mode while writing.
+%
+% proof -  All ``this doesn't fit'' warnings are active, as are
+%          references.  Overfull hboxes make ugly black blobs in
+%          the margin.  Use this mode to tidy up formatting after
+%          you're done writing.  (Same as article's ``draft'' mode.)
+%
+% final -  As proof, but the ugly black blobs are turned off.  Use
+%          this to render PDFs or PostScript to give to other people,
+%          when you're completely done.  (As with article, this is the
+%          default.)
+%
+% You can also use the leqno, fleqn, or openbib options to article.cls
+% if you wish.  None of article's other options will work.
+
+%%%
+%%% PLEASE CHANGE 'galley' to 'final' BEFORE SUBMITTING.  THANKS!
+%%% (to submit: "make clean" in the toplevel directory; tar and gzip *only* your directory;
+%%% email the gzipped tarball to papers@linuxsymposium.org.)
+%%%
+\documentclass[galley]{ols}
+
+% These two packages allow easy handling of urls and identifiers per the example paper.
+\usepackage{url}
+\usepackage{zrl}
+
+% The following package is not required, but is a handy way to put PDF and EPS graphics
+% into your paper using the \includegraphics command.
+\ifpdf
+\usepackage[pdftex]{graphicx}
+\else
+\usepackage{graphicx}
+\fi
+
+
+% Here in the preamble, you may load additional packages, or
+% define whatever macros you like, with the following exceptions:
+%
+% - Do not mess with the page layout, either by hand or with packages
+%   (e.g., typearea, geometry).
+% - Do not change the principal fonts, either by hand or with packages.
+% - Do not use \pagestyle, or load any page header-related packages.
+% - Do not redefine any commands having to do with article titles.
+% - If you are using something that is not part of the standard
+%   tetex-2 distribution, please make a note of whether it's on CTAN,
+%   or include a copy with your submission.
+%
+
+\begin{document}
+
+% Mandatory: article title specification.
+% Do not put line breaks or other clever formatting in \title or
+% \shortauthor; these are moving arguments.
+
+\title{Block Devices and Transport Classes: Where are we going?}
+\subtitle{ }  % Subtitle is optional.
+\date{}             % You can put a fixed date in if you wish,
+                    % allow LaTeX to use the date of typesetting,
+                    % or use \date{} to have no date at all.
+                    % Whatever you do, there will not be a date
+                    % shown in the proceedings.
+
+\shortauthor{James  Bottomley}  % Just you and your coauthors' names.
+% for example, \shortauthor{A.N.\ Author and A.\ Nother}
+% or perchance \shortauthor{Smith, Jones, Black, White, Gray, \& Greene}
+
+\author{%  Authors, affiliations, and email addresses go here, like this:
+James  Bottomley \\
+{\itshape Your affiliation}\\
+{\ttfamily\normalsize your-address@example.com}\\
+% \and
+% Bob \\
+% {\itshape Bob's affiliation.}\\
+% {\ttfamily\normalsize bob@example.com}\\
+} % end author section
+
+\maketitle
+
+\begin{abstract}
+% Article abstract goes here.
+\input{bottomley-abstract.tex}
+\end{abstract}
+
+% Body of your article goes here.  You are mostly unrestricted in what
+% LaTeX features you can use; however, the following will not work:
+% \thispagestyle
+% \marginpar
+% table of contents
+% list of figures / tables
+% glossaries
+% indices
+
+\end{document}
+