Re: make /dev/pci really readable

From: John-Mark Gurney (gurney_j_at_efn.org)
Date: 06/21/03

  • Next message: Scott Long: "API change for bus_dma" 
    Date: Fri, 20 Jun 2003 18:10:02 -0700
To: Bruce Evans <bde@zeta.org.au>, Robert Watson <rwatson@freebsd.org>, arch@freebsd.org

    John-Mark Gurney wrote this message on Mon, Jun 16, 2003 at 22:29 -0700:
    > Bruce Evans wrote this message on Tue, Jun 17, 2003 at 12:36 +1000:
    > > On Mon, 16 Jun 2003, Robert Watson wrote:
    > > > It looks like (although I haven't tried), user processes can
    > > > also cause the kernel to allocate unlimited amounts of kernel memory,
    > > > which is another bit we probably need to tighten down.
    > >
    > > Much more serious.
    >
    > Yep, the pattern_buf is allocated, and in some cases a berak happens
    > w/o freeing it. So there is a memory leak her. Will be fixed soon.

    Ok, I think I have a good patch. It's attached. Fixes the memory
    leak. I have also fix the pci manpage to talk about the errors, but
    it isn't included in the patch. 

    -- 
  John-Mark Gurney				Voice: +1 415 225 5579
     "All that I will do, has been done, All that I have, has not."

    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Scott Long: "API change for bus_dma"

    Relevant Pages

    • Re: remove zero_page (was Re: -mm merge plans for 2.6.24)
      ... then I'd certainly accept the patch. ... (basically -- if the app cares about memory or cache footprint and is using ... And indeed this cacheline bouncing has shown up on large SGI systems. ... Inserting a ZERO_PAGE for anonymous read faults appears to be a false ...
      (Linux-Kernel)
    • =?iso-8859-15?Q?Re:_[RFC]_BadRAM_still_not_ready_for_inclusion_=3F_(wa?= =?iso-8859-
      ... maybe this patch is just something very special, having many pro's but also con's - so this also could be one reason why it exists for so long outside mainline. ... BadRAM let's you tell the kernel to skip certain regions of ram, ... forever, once it becomes a supported feature, for the benefit of the few ... people who can't or won't replace bad memory. ...
      (Linux-Kernel)
    • [RFC PATCH 0/4]: affinity-on-next-touch
      ... I wrote a patch to support the adaptive data distribution strategy ... certain region of its virtual memory space. ... memory area from read and write accesses and install a signal handler to ... Afterwards, the signal handler clears the page protection ...
      (Linux-Kernel)
    • Re: [patch 00/19] VM pageout scalability improvements
      ... only does it use up CPU time, but it also provokes lock contention ... and can leave large systems under memory presure in a catatonic state. ... This patch series improves VM scalability by: ... segment for reclaimability. ...
      (Linux-Kernel)
    • Re: [patch 02/11] PAT x86: Map only usable memory in x86_64 identity map and kernel text
      ... The main thing required is on the lines of Jesse's patch. ... 32-bit: trim memory not covered by wb mtrrs ... On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all ...
      (Linux-Kernel)