[lkml]   [2002]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: Strange load spikes on 2.4.19 kernel
    > Not true.  While a block is being allocated on mounted
    > filesystem X on one cpu, a TCP packet can be being
    > processed on another processor and a block can be allocated
    > on mounted filesystem Y on another processor.

    Does anyone besides me notice that the more Dave and I argue the longer
    and longer the list of extenuating circumstances gets in order for Dave
    to continue to be right?

    In this email, I'm not right if the data is on separate partitions.

    Dave, do you realize how many people, despite advice to the contrary,
    put everything on one honk'in / partition? For all those people, I'm

    Dave, you're confusing the rule with the exceptions to the rule. I'm
    right as a general rule, and you're pointing out all the exceptions to
    the rule to try to prove that I'm wrong.

    > Actually, it can even be threaded to the point where
    > block allocations on the same filesystem can occur in
    > parallel as long as it is being done for different
    > block groups.

    Prove it. If you can code multi-threading SMP block and inode
    allocation using a non-preemptive kernel (which Linux is) ON THE SAME
    PARTITION, I will eat my hard drive.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:30    [W:0.019 / U:16.076 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site