Re: simplify disksort, please review.

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 06/09/05

  • Next message: Poul-Henning Kamp: "Re: RFC: Stack saving/tracing functionality." 
    To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Date: Thu, 09 Jun 2005 21:42:15 +0200

    In message <20050609193008.GB837@darkness.comp.waw.pl>, Pawel Jakub Dawidek writes:

    >The one example of how the order can be broken (write(offset, size)):
    >
    > write(1024, 512)
    > write(0, 2048)

    If you issue these two requests just like that, you get no guarantee
    which order they get written in.

    It's not just disksort which might surprise you, tagged queuing and
    write caches may mess up your day as well. 

    -- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Poul-Henning Kamp: "Re: RFC: Stack saving/tracing functionality."

    Relevant Pages