[9241] in linux-scsi channel archive
Re: NT [SCSI] class/filter driver equiv. for linux?
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Mon Jul 24 20:36:48 2000
Message-ID: <001401bff5d0$0826dab0$0f17a8c0@eric.home>
From: "Eric Youngdale" <eric@andante.org>
To: "Douglas Gilbert" <dougg@torque.net>, <sralston@lsil.com>
Cc: <linux-scsi@vger.rutgers.edu>
Date: Fri, 21 Jul 2000 19:13:57 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
----- Original Message -----
From: "Douglas Gilbert" <dougg@torque.net>
To: <sralston@lsil.com>
Cc: <linux-scsi@vger.rutgers.edu>
Sent: Monday, July 17, 2000 11:20 AM
Subject: Re: NT [SCSI] class/filter driver equiv. for linux?
> > Are there any mechanisms or methods for linux that would be
> > equivalent (or even functionally similar) to a NT SCSI
> > class/filter driver?
>
> Since I am not familiar with the NT/W2K SCSI driver architecture
> I went looking and found this url:
> http://www.microsoft.com/DDK/DDKdocs/Win2k/01scsidr_7yg7.htm
>
> At first glance it looks a bit like STREAMS/TLI. How do the
> optional filter drivers get configured?
This is a pretty fair description. NT is heavily object oriented and
(from what I have read, not that I have tried any of this) is very much like
a stack of drivers that get pushed down onto a stack. You can write filter
drivers to "massage" the requests, and the filters can be at several levels.
At one level, the filters can sit inbetween user requests and a filesystem,
they can also sit between the filesystem and the device driver.
I guess in a certain respect the md driver is sort of a linux equivalent
of a filter, but it is a specific purpose filter. Something similar along
those lines could probably be done, I guess.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
