Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Jul 2006 12:54:30 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Matthew Jacob <lydianconcepts@gmail.com>, csaba-ml@creo.hu, Bill Paul <wpaul@freebsd.org>, freebsd-current@freebsd.org, Christian Brueffer <brueffer@freebsd.org>
Subject:   Re: Call for stge(4) testers
Message-ID:  <20060710035430.GC1128@cdnetworks.co.kr>
In-Reply-To: <20060710030755.GN734@funkthat.com>
References:  <20060706124258.GE76865@cdnetworks.co.kr> <20060707045344.177AF16A4DD@hub.freebsd.org> <20060707074957.GF82406@cdnetworks.co.kr> <20060707094302.GA1669@haakonia.hitnet.RWTH-Aachen.DE> <7579f7fb0607082124p114dfd67r68a5f4db45eff5c2@mail.gmail.com> <20060710022737.GB1128@cdnetworks.co.kr> <20060710030755.GN734@funkthat.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 09, 2006 at 08:07:55PM -0700, John-Mark Gurney wrote:
 > Pyun YongHyeon wrote this message on Mon, Jul 10, 2006 at 11:27 +0900:
 > > On Sat, Jul 08, 2006 at 09:24:23PM -0700, Matthew Jacob wrote:
 > >  > Jason THorpe did one for NetBSD.
 > >  > 
 > >  > I did one for Solaris. Nice chip. Too bad it wasn't more popular.
 > > 
 > > I'm satisfied with the performance and easy interface for the chip.
 > > But the lack of Tx interrupt moderation and extra accesses to a
 > > status register to check which kind of Tx errors were occurred are
 > > serious fault. Since the the error condition uses the same status
 > > bit in interrupt status register it's hard to distingush failures
 > > from sucess without extra register accesses.
 > 
 > bah, tx interrupts are so last century... there isn't any reason to
 > have them... just schedule a timeout or wakeup a thread when the
 > number of tx descriptors are low.. and if you ran out, you could
 > even do the minimal work to free them up right in place...
 > 

I'm afraid it's not that simple. If we just reclaim Tx descriptors
based only on number of available Tx descriptors it would hold a lot
of mbuf chains in memory for a long time. My approach to solve this
is hybrid(a watermark which control when to raise a Tx interrupt
plus clean up handler which is called every hz)

-- 
Regards,
Pyun YongHyeon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060710035430.GC1128>