[7367] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

New SCSI queueing code.

daemon@ATHENA.MIT.EDU (Eric Youngdale)
Mon Oct 18 14:25:22 1999

Message-ID: <016501bf1993$b69afa00$940310ac@fairfax.datafocus.com>
From:   "Eric Youngdale" <eric@andante.org>
To:     <alan@lxorguk.ukuu.org.uk>,
        "Linux SCSI mailing list" <linux-scsi@vger.rutgers.edu>
Date:   Mon, 18 Oct 1999 14:07:51 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0162_01BF1972.2A1AD170"

This is a multi-part message in MIME format.

------=_NextPart_000_0162_01BF1972.2A1AD170
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


    I have updated my patches to work against 2.3.22, and these should =
be up on http://www.andante.org/scsi_queue.html.  I have also finished =
dealing with the single_lun case, which was the only outstanding outage =
that I am aware of.

    FWIW, I have tested it more extensively on my test system, and it =
seemed to stand up, at least until one of the disks that I was using for =
testing purposes died.   The previous problems that I was having with =
the aic7xxx driver went away when I switched to a newer Adaptec card - =
for some reason the interrupt line was getting stuck on with the old =
card, and I need to stay focussed on getting these patches shepherded =
into the distribution kernel.

    The testing that I have done with the live system was on 2.3.17 - I =
am getting bitten by an inability to assemble bootsect.s with 2.3.22 =
(.org directive moves IP backwards), and I need to browse linux-kernel =
to figure out what got broken and how to fix it.

    My thinking is that I would like to submit this into the main =
distribution kernel within the next two weeks or so, barring any =
problems or strong objections.   Given that it is possible for people to =
select the old queueing code at kernel config time, the main objective =
is to make it easier for people to test, and to reduce the number of =
stupid merge conflicts that I have to deal with.

-Eric



------=_NextPart_000_0162_01BF1972.2A1AD170
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I have updated my =
patches to=20
work against 2.3.22, and these should be up on <A=20
href=3D"http://www.andante.org/scsi_queue.html">http://www.andante.org/sc=
si_queue.html</A>.&nbsp;=20
I have also finished dealing with the single_lun case, which was the =
only=20
outstanding outage that I am aware of.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; FWIW, I have tested =
it more=20
extensively on my test system, and it seemed to stand up, at least until =
one of=20
the disks that I was using for testing purposes died.&nbsp;&nbsp; The =
previous=20
problems that I was having with the aic7xxx driver went away when I =
switched to=20
a newer Adaptec card - for some reason the interrupt line was getting =
stuck on=20
with the old card, and I need to stay focussed on getting these patches=20
shepherded into the distribution kernel.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; The testing that I =
have done=20
with the live system was on 2.3.17 - I am getting bitten by an inability =
to=20
assemble bootsect.s with 2.3.22 (.org directive moves IP backwards), and =
I need=20
to browse linux-kernel to figure out what got broken and how to fix=20
it.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; My thinking is that =
I would like=20
to&nbsp;submit this into the main distribution kernel within the next =
two weeks=20
or so, barring any problems or strong objections.&nbsp;&nbsp; Given that =
it is=20
possible for people to select the old queueing code at kernel config =
time, the=20
main objective is to make it easier for people to test, and to reduce =
the number=20
of stupid merge conflicts that I have to deal with.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-Eric</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0162_01BF1972.2A1AD170--


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post