Re: Thou shalt have no other gods before the ANSI C standard

From: David Wagner (daw_at_taverner.cs.berkeley.edu)
Date: 02/16/05 

Date: Wed, 16 Feb 2005 17:24:54 +0000 (UTC)

Paul Rubin wrote:
>One of DJB's more was that if you count objects like network byte
>streams that don't have to fit in memory, then size_t might not
>be big enough to express their size, and on 32-bit machines this
>has already caused problems in real existing programs.

Fair enough. But right now I don't think his code can operate on
out-of-memory data. I'd say that if he changes his code so that it
doesn't require the entire object to be in memory at once, then he should
pick something bigger than a size_t, but until then, I have a hard time
seeing the argument for something other than a size_t.

Relevant Pages

  • Re: SCO 5.0.7 MP5 network hung up
    ... configured memory, I'm thinking this isn't a STREAMS failure at all. ... you have a small STREAMS failure problem that probably ... There's another point of total failure in the network stack: ... reduce STREAMS memory allocation? ...
    (comp.unix.sco.misc)
  • [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
    ... Convergence of network and storage paths" ... "Net vm deadlock fix " ... Maybe it is another memory deadlock, ... dipping into the memalloc reserve if it must. ...
    (Linux-Kernel)
  • Re: [PATCH] [Request for inclusion] Filesystem in Userspace
    ... > to allocate network buffers down to the PF_MEMALLOC boundary. ... > the network stack is only allowed to allocate memory down to the ... A lot of people think that mempool solves this problem, ... normal allocation, but that fails, so they start eating into the mempool ...
    (Linux-Kernel)
  • Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
    ... then you should not kill the other things that want memory. ... The users of memory are various subsystems. ... the network subsystem because its build on kmalloc! ... The reserves are spread over all kernel mapped zones, ...
    (Linux-Kernel)
  • Re: Odd performance problems after upgrade from 4.11 to 6.0-Stable
    ... After the upgrade, the system performs poorly. ... job produced minimal CPU utilization and little progress. ... My network link only ran at 3.4 Mbps (yes, that's bits, not ... runs out of memory and starts to use the swap file. ...
    (freebsd-stable)