On 2013/04/12, at 22:31, Scott Long wrote:
> On Apr 12, 2013, at 7:43 PM, Rui Paulo wrote:
>
>> On 2013/04/11, at 13:18, Gleb Smirnoff wrote:
>>
>>> Lack of maintainer in a near future would lead to bitrot due to changes
>>> in other areas of network stack, kernel APIs, etc. This already happ
On Fri, Apr 12, 2013 at 11:31:09PM -0600, Scott Long wrote:
>
> On Apr 12, 2013, at 7:43 PM, Rui Paulo wrote:
>
> > On 2013/04/11, at 13:18, Gleb Smirnoff wrote:
> >
> >> Lack of maintainer in a near future would lead to bitrot due to changes
> >> in other areas of network stack, kernel APIs,
On Apr 12, 2013, at 7:43 PM, Rui Paulo wrote:
> On 2013/04/11, at 13:18, Gleb Smirnoff wrote:
>
>> Lack of maintainer in a near future would lead to bitrot due to changes
>> in other areas of network stack, kernel APIs, etc. This already happens,
>> many changes during 10.0-CURRENT cycle were
Baptiste Daroussin wrote:
> On Fri, Apr 12, 2013 at 12:56:10PM +, Eggert, Lars wrote:
> > Hi,
> >
> > On Apr 12, 2013, at 1:10, Rick Macklem wrote:
> > > Well, I have no idea why an NFS server would reply errno 70 if the
> > > file
> > > still exists, unless the client has somehow sent a bogus
On 2013/04/11, at 13:18, Gleb Smirnoff wrote:
> Lack of maintainer in a near future would lead to bitrot due to changes
> in other areas of network stack, kernel APIs, etc. This already happens,
> many changes during 10.0-CURRENT cycle were only compile tested wrt
> ipfilter. If we fail to find m
On Fri, 2013-04-12 at 16:14 -0700, Jim Harris wrote:
> On Fri, Apr 12, 2013 at 3:35 PM, FreeBSD Tinderbox
> wrote:
>
> > >>> World build completed on Fri Apr 12 22:33:43 UTC 2013
> > TB --- 2013-04-12 22:33:43 - generating LINT kernel config
> > TB --- 2013-04-12 22:33:43 - cd /src/sys/amd64/conf
On Fri, Apr 12, 2013 at 3:35 PM, FreeBSD Tinderbox wrote:
> >>> World build completed on Fri Apr 12 22:33:43 UTC 2013
> TB --- 2013-04-12 22:33:43 - generating LINT kernel config
> TB --- 2013-04-12 22:33:43 - cd /src/sys/amd64/conf
> TB --- 2013-04-12 22:33:43 - /usr/bin/make -B LINT
> TB --- 201
TB --- 2013-04-12 18:51:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-12 18:51:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-04-12 18:51:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-12 18:51:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-04-12 18:51:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-12 18:51:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hello, John.
You wrote 10 апреля 2013 г., 0:08:09:
JB> Can you assign different interrupts via the BIOS somehow?
I've tried it! And! I'm SHOCKED: this MoBo try to use some strange
mode in BIOS Setup, which isn't supported by screen, installed where
this router installed now! It looks like text
In message <201304121214.32331@freebsd.org>, John Baldwin writes:
John,
Quite frankly I don't think you have the age to teach me about
ISA multiport serial cards :-)
>Multiport isa(4) cards were not as generic as PCI cards, so we have several
>different drivers for those (rc, digi, cy) [...
On Thursday, April 11, 2013 5:37:48 pm Poul-Henning Kamp wrote:
> In message <201304111050.37055@freebsd.org>, John Baldwin writes:
>
> >> Though if these ports don't have the logic that the AST cards did to
> >> share the IRQ, that'd make it hard...
> >>
> >> The sio man page talks about thi
In message <98147894.20130412171...@serebryakov.spb.ru>, Lev Serebryakov writes
:
> I mean, there is no good way to distinguish between this (hardware)
> implementation and "true" 4 single UART chips, when it is identify
> itself as "generic 16550 UART", 4 times, at 4 I/O addresses.
That is a ker
Hello, Poul-Henning.
You wrote 12 апреля 2013 г., 1:37:48:
PHK> I think you are mistaken, the 4 uarts are in the same chip and I am
PHK> sure they have done something sensible with the interrupts so they
PHK> can be shared.
I mean, there is no good way to distinguish between this (hardware)
impl
On Fri, Apr 12, 2013 at 12:56:10PM +, Eggert, Lars wrote:
> Hi,
>
> On Apr 12, 2013, at 1:10, Rick Macklem wrote:
> > Well, I have no idea why an NFS server would reply errno 70 if the file
> > still exists, unless the client has somehow sent a bogus file handle
> > to the server. (I am not a
Hello, Poul-Henning.
You wrote 12 апреля 2013 г., 1:37:48:
>>These are multiport cards and something like puc or digi, etc. is fine for
>>those. The OP's issue is that he has a board with 4 independent 16550
>>UARTs which are attempting to share IRQs. Those are not multiport cards
>>and are thus
Hi,
On Apr 12, 2013, at 1:10, Rick Macklem wrote:
> Well, I have no idea why an NFS server would reply errno 70 if the file
> still exists, unless the client has somehow sent a bogus file handle
> to the server. (I am not aware of any client bug that might do that. I
> am almost suspicious that t
Hello,
the patch removes memory contention and data loss on packets/bytes
statistics in lagg(4) driver, utilizing counter(9).
Any benchmarking reports with trunk built upon 10Gbit interfaces
would be much appreciated.
Sorry, but patch isn't tested except compiling. I don't have a
lab to
Hello,
the patch reduces number of atomic(4) operations in ng_netflow(4),
utilizing counter(9) and makes some previously 32-bit counters 64-bit.
Any test reports appreciated.
--
Totus tuus, Glebius.
Index: netflow.c
===
--- n
20 matches
Mail list logo
