mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DAC960 Bitrot
Date: Wed, 24 Jul 2002 18:57:51 +0200	[thread overview]
Message-ID: <E17XPSR-0007tD-00@starship> (raw)
In-Reply-To: <20020724143931.GG5159@suse.de>

On Wednesday 24 July 2002 16:39, Jens Axboe wrote:
> The only changes I did to this driver where trivial conversions in the
> 2.5.1-pre days, in fact even before multi-page bio's existed. This,
> btw, is also something you should keep an eye out for -- multi-page bio
> support is currently broken.

I spotted that.  I changed bio_size (which is gone) to bio_sectors(bio) << 9, 
is this correct?

> I would suggest also moving DAC960 to the
> pci dma api (this is a must) and then move it to use the generic block
> helpers for mapping requests. That way there isn't a lot of nasty
> duplication there as well, plus it will automatically get the multi-page
> issues right.

My first concern is to get something working any way I can so that I can 
start doing regression testing.  True/false: the bad old way of doing dma 
will still work, it's just deprecated?  If true, then I should (trivially) 
switch back to the old way of doing things, get the rest working, then 
convert to the dma api.  Maybe *you* could make all the changes at the same 
time and expect to end up with something that works, but I can't.

The alternative is to go back many kernel versions and find the first one  
that broke something, but I don't want to do that because too much else was 
broken at the time.

> Hmm, is DAC960 using a full major per controller?!

As you saw, it implements the top level block interface instead of being a 
scsi device as it should be.  So for disk subsystems we have: 1) IDE 2) SCSI 
3) DAC960.  Eep.  At some point it's all going to be SCSI, right?

-- 
Daniel

  parent reply	other threads:[~2002-07-24 16:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06  5:31 [PATCH][RFT](2) minimal rmap for 2.5 - akpm tested Rik van Riel
2002-07-06  6:28 ` Andrew Morton
2002-07-06 19:06   ` Linus Torvalds
2002-07-06 20:00     ` Andrew Morton
2002-07-06 20:11       ` Linus Torvalds
2002-07-10 17:35 ` Sebastian Droege
2002-07-10 20:42   ` Rik van Riel
2002-07-10 21:56     ` Daniel Phillips
2002-07-11  6:47       ` Jens Axboe
2002-07-11  9:58         ` Daniel Phillips
2002-07-11 10:08           ` Jens Axboe
2002-07-22 22:02             ` DAC960 Bitrot Daniel Phillips
2002-07-24 14:39               ` Jens Axboe
2002-07-24 14:48                 ` Jens Axboe
2002-07-24 16:19                 ` Wakko Warner
2002-07-24 16:57                 ` Daniel Phillips [this message]
2002-07-24 17:02                   ` Jens Axboe
2002-07-24 17:30                     ` Alexander Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E17XPSR-0007tD-00@starship \
    --to=phillips@arcor.de \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®