Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Nov 2006 22:09:34 +0100
From:      "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Ruslan Ermilov <ru@FreeBSD.org>, freebsd-stable@FreeBSD.org
Subject:   Re: nfe: can not cvs sources anymore!
Message-ID:  <4560C80E.7020402@mail.zedat.fu-berlin.de>
In-Reply-To: <20061119201341.GA1381@xor.obsecurity.org>
References:  <4560657A.9000002@mail.zedat.fu-berlin.de>	<20061119161749.GB31926@rambler-co.ru>	<4560A1A5.4050500@mail.zedat.fu-berlin.de> <20061119201341.GA1381@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote:
> On Sun, Nov 19, 2006 at 07:25:41PM +0100, O. Hartmann wrote:
>   
>> Ruslan Ermilov wrote:
>>     
>>> On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote:
>>>   
>>>       
>>>> Hello.
>>>> Using these two sources for getting nfe() driver support for my FreeBSD
>>>> 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big
>>>> interrupt problems using the nve() driver.
>>>> But with yesterday, I can't get the sources anymore. nfe() isn't yet a
>>>> part of the 6.2 BETA, that's what I looked first for, so can anybody
>>>> help me out? Is nfe() a part of 6.2-REL in the near future or are there
>>>> other reasons stop spreading the sources via that cvs source?
>>>>
>>>> Thanks for your help in advance,
>>>>
>>>>     
>>>>         
>>> Did you try the version at
>>> http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html
>>> ?  I use it and except for some peer-to-peer gigabit problems I
>>> didn't notice any other bad signs.  It's far more stable that
>>> what we have now in the CVS tree.
>>>
>>>
>>> Cheers,
>>>   
>>>       
>> Thank you for the link.
>> No, I did not try this link since I thought the CVS tree's version was
>> the stabelst version we have. I find it convenient by pushing it via net
>> using cvs just after I upgraded my CVS tree of the sources for the
>> operating system. I will keep this link in mind.
>> Is there a date we can this driver expect in FreeBSD 6.2? Or is the
>> driver more subject to be merged in 6.2-STABLE and for 6.3? nve() isn't
>> suitable, neither with SCHED_ULE (which I use now again) and with
>> SCHED_4BSD, because on my hardware platform the interrupt generation is
>> much higher than that of the nfe() driver - and due to this massive
>> interrupts useless for me.
>>     
>
> Please remember to turn off SCHED_ULE before submitting any and all
> future bug reports, thanks :-)
>
> Kris
>   


Well, yes, I do this, and as I wrote above, the problem ist even worse with SCHED_4BSD. And SCHED_ULE is now my defaukt, beacause FreeBSD 6.2-PRE/AMD64 ADN i386 is as freezing for short periods of times as never seen before ...

Regards,
Oliver




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