Tuesday 28 of October 2008 19:10:43 Alexander Motin napisał(a):
> Bartosz Giza wrote:
> >> The CPU time you see there includes much more then just a card
> >> handling itself. It also includes CPU time of the most parts of
> >> network stack used to process received packet. So if you have NAT, big
Bartosz Giza wrote:
> Tuesday 28 of October 2008 19:10:43 Alexander Motin napisał(a):
>> Bartosz Giza wrote:
The CPU time you see there includes much more then just a card
handling itself. It also includes CPU time of the most parts of
network stack used to process received packet. S
This is indeed the problem, thanks.
Is this a known issue with FreeBSD-7.0 ?
I do not want to hide a potential bug in the NIC driver.
Eitan Shefi
-Original Message-
From: John-Mark Gurney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 11:02 PM
To: Eitan Shefi
Cc: freebsd-ne
Wednesday 29 of October 2008 11:36:45 Alexander Motin napisał(a):
> Bartosz Giza wrote:
> > Tuesday 28 of October 2008 19:10:43 Alexander Motin napisał(a):
> >> Bartosz Giza wrote:
> The CPU time you see there includes much more then just a card
> handling itself. It also includes CPU tim
Bartosz Giza wrote:
> So now i am lost again. If packet filtering on bge card is counted to irq17:
> bge0 process so i think it should use more cpu.
> From what you wrote there should be no difference for me if card use tasq
> or irq. Those processes do exactly the same thing? If that is true so
Old Synopsis: 6.4-RC1 Boot Fails if NFS Hostname cannot be resolved (mount_nfs)
New Synopsis: [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be resolved
(mount_nfs)
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Oct 29 16:01:4
Eitan Shefi wrote this message on Wed, Oct 29, 2008 at 11:34 +0200:
> This is indeed the problem, thanks.
>
> Is this a known issue with FreeBSD-7.0 ?
> I do not want to hide a potential bug in the NIC driver.
This is a known issue since I fixed the transmit code not to munge the
route's MTU so t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You nailed it ... I was missing the 'tap.up_on_open=1' ... once I put that in
place, it works like a charm ...
Thanks ...
- --On Tuesday, October 28, 2008 22:37:58 -0700 Bakul Shah <[EMAIL PROTECTED]>
wrote:
> On Wed, 29 Oct 2008 01:38:38 -0300 "