Re: User space out of memory approach

From: Marcelo Tosatti (marcelo.tosatti_at_cyclades.com)
Date: 01/11/05

  • Next message: selvakumar nagendran: "pipe_wait illustration needed"
    Date:	Tue, 11 Jan 2005 05:42:30 -0200
    To: Thomas Gleixner <tglx@linutronix.de>
    
    

    On Tue, Jan 11, 2005 at 01:35:47AM +0100, Thomas Gleixner wrote:
    > On Mon, 2005-01-10 at 18:05 -0200, Marcelo Tosatti wrote:
    > > The feature is interesting - several similar patches have been around with similar
    > > functionality (people who need usually write their own, I've seen a few), but none
    > > has ever been merged, even though it is an important requirement for many users.
    >
    > It's not a requirement for users. The current implementation in the
    > kernel it's just broken, ugly code.
    >
    > > This is simple, an ordered list of candidate PIDs. IMO something similar to this
    > > should be merged. Andrew ?
    >
    > I have no objections against the userspace provided candidate list
    > option, but as long as the main sources of trouble
    >
    > - invocation
    > - reentrancy
    > - timed, counted, blah ugly protection
    > - selection problem
    >
    > are not fixed properly, we don't need to discuss the inclusion of a
    > userspace provided candidate list.
    >
    > Postpone this until the main problem is fixed. There is a proper
    > confirmed fix for this available. It was posted more than once.

    Agreed - haven't you and Andrea fixed those recently ?

    > Merging a fix which helps only 0,001 % of the users to hide the mess
    > instead of fixing the real problem is a real interesting engineering
    > aproach.
    >
    > I don't deny, that after the source of trouble is fixed it is worth to
    > think about the merging of this addon to allow interested users to
    > define the culprits instead of relying on an always imperfect selection
    > algorithm.

    Yep.
    -
    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: selvakumar nagendran: "pipe_wait illustration needed"

    Relevant Pages

    • Re: [1/1][PATCH] nproc v2: netlink access to /proc information
      ... > The presumed wrong assumptions underlying broken tools of the future ... > making it easy to write correct applications (or in fixing broken apps ... knowledge of the CONFIG_MMU usage models and/or whatever userspace ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: User space out of memory approach
      ... confirmed fix for this available. ... Merging a fix which helps only 0,001 % of the users to hide the mess ... instead of fixing the real problem is a real interesting engineering ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: 2.6.0-test4 - lost ACPI
      ... We've had trouble with Award/VIA in this ... 3-year old Award/VIA BIOS. ... >> dmesg output. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: finding out the value of HZ from userspace
      ... > When we go to a tickless kernel and offer high-resolution timers to ... is the value of HZ reported to userspace anywhere? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Filesystem linking protections
      ... > has broken atd and courier in the past. ... > or O_EXCL so there's work to be done in userspace. ... Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)