Re: irq handling in DDE Linux26

On 10-5-7 上午7:51, olafbuddenha...@gmx.net wrote: > Hi, > > On Fri, May 07, 2010 at 12:53:20AM +0800, Da Zheng wrote: > >> disable_irq_nosync_lockdep_irqsave is exactly the same as >> disable_irq_nosync when there isn't CONFIG_LOCKDEP. It seems to me >> that ne2k-pci shouldn't call it in the first

[bug #29809] creating a firmlink loop results in memory exhaustion

Follow-up Comment #1, bug #29809 (project hurd): As suggested by antrik in #hurd here is a log of the port usage of both ext2fs and firmlink (both eat up more and more memory) measured once every second using portinfo $PID | wc --lines: r...@hurdbox:~# ps ax | egrep '(ext2fs|firmlink)' root

Re: irq handling in DDE Linux26

Hi, On Fri, May 07, 2010 at 12:53:20AM +0800, Da Zheng wrote: > disable_irq_nosync_lockdep_irqsave is exactly the same as > disable_irq_nosync when there isn't CONFIG_LOCKDEP. It seems to me > that ne2k-pci shouldn't call it in the first place when transmitting > packets, but Linux drivers should

[bug #29809] creating a firmlink loop results in memory exhaustion

URL: Summary: creating a firmlink loop results in memory exhaustion Project: The GNU Hurd Submitted by: teythoon Submitted on: Thu 06 May 2010 05:09:09 PM GMT Category: Hurd

irq handling in DDE Linux26

Hello, In DDE Linux26, the interrupt is ignored when an interrupt line is disabled, i.e., the handle_irq field of ddekit_irq_ctrl is 0. In ne2k-pci, an example in DDE Linux26, when a packet is transmitted by the driver, disable_irq_nosync_lockdep_irqsave() is called to disable irq. Then it trigge