[lkml]   [2006]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Raid 0 Swap?

    >> I thought kernel data weren't swapped at all?

    If the swap code was swapped, who would swap it in again?

    >Well, it's not that simple. Kernel uses both swappable and
    >non-swappable memory internally. For some things, it's
    >unswappable, for some, it's swappable. In general, it's
    >impossible to say which parts of kernel will break (and
    >in wich ways) if swap goes havoc.

    In general, everything you type in as C code (.bss, .data, .text) should be
    unswappable. kmalloc()ed areas are resident too, and kmalloc has a
    parameter which defines whether the allocation can/cannot push userspace
    pages into the swap (GFP_ATOMIC/GFP_IO). So if there is some
    kernel-allocation swapped out, it is most likely to be marked as
    'userspace' so that the same algorithms can be used for swapin and -out.

    Jan Engelhardt

    VGER BF report: H 5.48632e-07
    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: 2006-09-04 12:51    [W:0.028 / U:80.496 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site