Re: [RFC] Arch option to touch newly allocated pages

• Next message: Andrew Morton: "Re: [RFC] Arch option to touch newly allocated pages"
• Previous message: Florian Weimer: "Re: Petition Against Official Endorsement of BitKeeper by Linux Maintainers"
• In reply to: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Next in thread: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Reply: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

alan@lxorguk.ukuu.org.uk said:
> Not having a fallback is unacceptable. Thats the real problem. You
> can't go around pandering to sloppy coders who can't work a memory
> allocator

OTOH there is perhaps some justification for distinguishing between 'If you
fail this I'll tell the user -ENOMEM and continue happily on my way'
allocations and 'If you fail this I lose track of hardware state and all is
fucked till we reboot' ones.

--
dwmw2
-
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: Andrew Morton: "Re: [RFC] Arch option to touch newly allocated pages"
• Previous message: Florian Weimer: "Re: Petition Against Official Endorsement of BitKeeper by Linux Maintainers"
• In reply to: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Next in thread: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Reply: Alan Cox: "Re: [RFC] Arch option to touch newly allocated pages"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:01:10 EST