Re: Silicon Image 3112A SATA trouble

From: Bartlomiej Zolnierkiewicz (B.Zolnierkiewicz_at_elka.pw.edu.pl)
Date: 11/30/03

  • Next message: Jeff Garzik: "Re: Silicon Image 3112A SATA trouble" 
    To: Jens Axboe <axboe@suse.de>, Jeff Garzik <jgarzik@pobox.com>
Date:	Sun, 30 Nov 2003 17:58:53 +0100

    On Sunday 30 of November 2003 17:51, Jens Axboe wrote:
    > On Sun, Nov 30 2003, Jeff Garzik wrote:
    > > Jens Axboe wrote:
    > > >On Sun, Nov 30 2003, Bartlomiej Zolnierkiewicz wrote:
    > > >>Hmm. actually I was under influence that we have generic ioctls in
    > > >> 2.6.x, but I can find only BLKSECTGET, BLKSECTSET was somehow lost.
    > > >> Jens?
    > > >
    > > >Probably because it's very dangerous to expose, echo something too big
    > > >and watch your data disappear.
    > >
    > > IMO, agreed.
    > >
    > > Max KB per request really should be set by the driver, as it's a
    > > hardware-specific thing that (as we see :)) is often errata-dependent.

    Yep.

    > Yes, it would be better to have a per-drive (or hwif) extra limiting
    > factor if it is needed. For this case it really isn't, so probably not
    > the best idea :)
    >
    > > Tangent: My non-pessimistic fix will involve submitting a single sector
    > > DMA r/w taskfile manually, then proceeding with the remaining sectors in
    > > another r/w taskfile. This doubles the interrupts on the affected
    > > chipset/drive combos, but still allows large requests. I'm not terribly
    >
    > Or split the request 50/50.

    We can't - hardware will lock up.

    --bart

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Jeff Garzik: "Re: Silicon Image 3112A SATA trouble"

    Relevant Pages

    • Re: [PATCH] cpqarray update
      ... >>registered interfaces in the driver itself, but IMO far more important ... >>to propagate fatal errors back to the original caller. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.4.22-rc2 ext2 filesystem corruption
      ... > force the driver to use the lower DMA speed. ... > report on that when your request for the explicit test arrived, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Points to fs architecture
      ... > review the request is passed on to the entity that would have received it had my utility not been installed, ... Where can I find documentation on how to code drivers for the Linux kernel and about how the entire ... Linux USB Mass Storage Driver ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: [PATCH] - MPT FUSION - SPLITTING SCSI HOST DRIVERS
      ... That means the new SPI stub ... I'm not clear on this request. ... whether keeping the naming of mptscsih.ko driver would cause ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [Alsa-devel] Re: + v4l-720-alsa-support-for-saa7134-that-should-work-fix.patch added to -mm tree
      ... >> This is OK, IMO. ... it's up to the driver. ... newer patch addressing most of the points that Takashi and Lee showed. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)