On Thu, May 16, 2024 at 02:02:52PM +0100, Lexi Winter wrote:
> Scott:
> > I use RIPv2 for it's simplicity and small memory and CPU requirements. It
> > has its place and shouldn't be considered "legacy" despite its
> > shortcomings.
> > It&#
it. As a user I definitely see the value. I
understand that there is always a cost to providing code, but that wasn't
suggested as a reason. All APIs, modules, utilities, etc. need to regularly
justify their presence in the OS.
If it must be removed, is there any way to fork the FreeBSD routed and
route6d to a port? Or would that defeat the purpose of removing it in the
first place?
Scott
Hi,
Sorry, I was trying :
route delete -net 61.177.172.137 gw 127.0.0.1
that didn't work, but apparently
route delete -net 61.0.0.1 gw 127.0.0.1
has. Thanks!
Tuc
On Thu, Feb 15, 2018 at 12:51 PM, Lee Brown wrote:
> On Thu, Feb 15, 2018 at 9:47 AM, Scott Ellentuch
> wrot
5, 2018 at 9:47 AM, Scott Ellentuch
> wrote:
>
> > Hi,
> >
> > I did a very foolish thing
> >
> > route add -net 61.177.172.137 gw 127.0.0.1
> >
> >
> > 1) Thats not a net, thats a host
> > 2) Thats my Linux's syntax, not wha
Hi,
I did a very foolish thing
route add -net 61.177.172.137 gw 127.0.0.1
1) Thats not a net, thats a host
2) Thats my Linux's syntax, not what I expected
So now I have the following in my netstat -rn
61.0.0.1&0x7f01 MY.GW.IP.HERE UGSc10 fxp0
And I don't know
option you can
pursue that will definitely work.
*[image: userimage]Scott Larson[image: los angeles]
<https://www.google.com/maps/place/4216+Glencoe+Ave,+Marina+Del+Rey,+CA+90292/@33.9892151,-118.4421334,17z/data=!3m1!4b1!4m2!3m1!1s0x80c2ba88ffae914d:0x14e1d00084d4d09c>Lead
Systems Admini
, but they came out essentially in a dead heat when testing for
raw throughput.
*[image: userimage]Scott Larson[image: los angeles]
<https://www.google.com/maps/place/4216+Glencoe+Ave,+Marina+Del+Rey,+CA+90292/@33.9892151,-118.4421334,17z/data=!3m1!4b1!4m2!3m1!1s0x80c2ba88ffae914d:0x14e1d00084d4d
no problem.
*[image: userimage]Scott Larson[image: los angeles]
<https://www.google.com/maps/place/4216+Glencoe+Ave,+Marina+Del+Rey,+CA+90292/@33.9892151,-118.4421334,17z/data=!3m1!4b1!4m2!3m1!1s0x80c2ba88ffae914d:0x14e1d00084d4d09c>Lead
Systems Administrator[image: wdlogo] <https://www.wir
ts and NIC counters show any drops or errors? On the FBSD servers you
could also run 'netstat -i -w 1' under load to see if drops are occurring
locally, or 'systat -vmstat' for resource contention problems. But again, a
similar setup here and no such issues have appeared.
*
Thanks Navdeep, I figured there had to be more going on than just
allowing packets across interfaces. With forwarding automatically disabling
TSO/LRO that would entirely explain why my bandwidth throughput tests drop
off significantly.
*[image: userimage]Scott Larson[image: los angeles
On 4/23/2015 11:26 AM, Matthew Grooms wrote:
On 4/22/2015 8:34 PM, Scott O'Connell wrote:
I tried your suggestions.
I was successful in changing the vmhost01 bridge to include vlan100
and tap0, and in the vm (dev) binding the address directly to vtnet0.
On the VMHOST:
tap0: flags
Thanks for your reply, Matthew. See results below:
On 4/22/2015 4:17 PM, Matthew Grooms wrote:
On 4/22/2015 11:02 AM, Scott O'Connell wrote:
I'm very new to bhyve and am having an issue. I'm trying to get VM's
and VLAN's working.
I'm able to get VLAN's
I'm very new to bhyve and am having an issue. I'm trying to get VM's and
VLAN's working.
I'm able to get VLAN's working in a VM, but the VM and the VMHOST, can't
communicate with each other on the same vlan.
Using 10.1-RELEASE-p9 for both VMHOST01 and DEV. Upstream from the
VMHOST on lagg0 i
rwarding does to the network stack. Does it ultimately put a lower
priority on traffic where the server functioning as the packet router is
the final endpoint in exchange for having more resources available to route
traffic across interfaces as would generally be the case?
*[image: userimage]Scott Larso
of our
CPU processing right now is spent in TCP (with the rest being spent in the VM,
but that’s a different matter).
FWIW, Randall has some optimizations in this area of the stack. They aren’t
huge, IIRC they’re only a few percent, but worth looking at.
Scott
signature.asc
Description: Message signed with OpenPGP using GPGMail
ll about long-term data
>> stability.
>
> 3) should no longer be an issue. rmlocks now have full WITNESS and assertion
> support (including an rm_assert).
>
> However, one thing to consider is that rmlocks pin readers to CPUs while the
> read lock is held (which rwlock
PU instance, I can't imagine why
it would be useful for these flows to be different. However, I'm still a n00b
at
this networking stuff, so please correct me if I'm wrong.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists
ut this
> />/requires much more work, and unfortunately ABI change, so temporarily
> />/patch lagg(4) manually.
> />//>/We store counters in the softc, and once per second push their
> values
> />/to legacy ifnet counters./
>
Some sort of gatekee
Yup, it's an incredibly unsafe pattern. It also leads to the pattern where
auxiliary processing is handed off to a taskqueue, which then interleaves
the lock ownership with the ithread and produces out-of-order packet
reception.
Scott
On Aug 8, 2013, at 5:18 PM, Adrian Chadd wrote:
>
ge
sis
sk
sk
sn
snc
ste
stge
ti
tl
tsec
tx
txp
usb
usb
vge
virtio
vr
vte
vx
wb
wl
xe
xl
Sure a lot of these are very legacy. But there's a lot in here's that are not.
bge, bce, e1000, ixgbe, virtio, etc, probably more that I'm not catching in
this quick pass.
Scott
_
o sleep. That
means
no sx locks and no malloc(M_WAITOK), along with the obvious tsleep/msleep.
Taskqueues
have no such restriction.
An even rore relevant difference is that taskqueues have a much stronger
management API. Ithreads can only be scheduled by generating a hardware
interrupt,
can
, it's up to the driver to pause and drain the
RX processing prior to this state change. It worked well when I did it in
if_em, and it appears to work well with cxgbe.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mail
ocessing. TX dispatch is a different matter, but I don't think that it would
be
hard to have the if_transmit/if_start path respond to control synchronization
events.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailma
ew quad port adapters on PCIE Gen 3 give you 8GT/s bandwidth
> for
> the device. I'm not sure if you could buy the 82598 but I surely would not
> recommend
> it to anyone :)
FWIW, sometimes these kinds of cards are interesting if your primary interest is
link failover instead
We use both the chelsio and intel offerings
Scott
On Jul 25, 2013, at 2:10 PM, "Alexander V. Chernikov"
wrote:
> On 25.07.2013 00:26, Boris Kochergin wrote:
>> Hi.
> Hello.
>>
>> I am looking for recommendations for a 10gbps NIC from someone who has
>
Adrian, you're killing my spam filter! But yes, our use of FreeBSD at Netflix
is hardly a science project. Http://openconnect.netflix.com
Scott
On Jul 21, 2013, at 1:31 PM, Adrian Chadd wrote:
> Barney,
>
> I now work at netflix. We push >10gig per box. I'm working
enable_aim=0
NAS workloads are extremely sensitive to latency, and interrupt moderation
only adds latency. We tune some other things as well at Netflix and manage
to get quite good performance, though with a fairly different workload. Let
me know
We run bird for this task. Can't say if it works on 10 since he haven't
moved to 10 yet, but there have been some experiments with running
a 10 kernel in the 9 userland and bird seems to behave fine with that.
Scott
On Jun 29, 2013, at 1:50 PM, Peter Wemm wrote:
> I'm looki
amed diatribes and insults from him, with a brief smattering here and there
of
benign but content-free posts.
On the other hand, if the consensus here is to keep on baiting and feeding him
for
our own amusement, I applaud the effort but ask for a bit more subtlety =-)
Thanks!
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On Apr 15, 2013, at 1:27 PM, Cy Schubert wrote:
> In message , Scott Long
> writes:
>>
>> On Apr 15, 2013, at 11:48 AM, Cy Schubert wrote:
>>
>>> In message <18df99b0-6e66-4906-a233-7778451b8...@felyko.com>, Rui Paulo
>>> writes:
>>
lter would
> be a loss.
>
If you're committed to maintaining IPFilter, that's great. However, it can't be
left to stagger along in a zombie state with nothing more than good intentions
from well meaning people. What is your timeline for getting it back into shape
and re-in
uld be set about a fair amount of stuff in
FreeBSD,
but IPFilter stands out since there's a high rate of needed change happening in
the network stack, and it shouldn't be left to rot nor to be a stumbling block
for
those changes.
Scott
On Apr 15, 2013, at 12:49 PM, "Sam Fourman Jr.
On Apr 14, 2013, at 7:20 AM, Joe wrote:
> Rui Paulo wrote:
>> 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:
>>>>
>>>>&g
On Apr 13, 2013, at 11:43 AM, Rui Paulo wrote:
> On 2013/04/13, at 5:03, Scott Long wrote:
>> You target audience for this isn't people who track CURRENT, it's people who
>> are on 7, 8, or 9 and looking to update to 10.x sometime in the future.
>
> Yes, I&#
On Apr 13, 2013, at 12:33 AM, Rui Paulo wrote:
> 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 fu
filter is available but
deprecated/unsupported in FreeBSD 10, and will be removed from FreeBSD 11.
Certain people will still pitch a fit about it departing, but if the tools are
there to help the common users, you'll be successful in winning mindshare and
general support.
Scott
_
Comedy gold. It's been a while since I've seen this much idiocy from you,
Barney. Hopefully the rest of the mailing list will blackhole you, as I'm
about to, and we can all get back to real work.
Scott
On Mar 29, 2013, at 10:38 AM, Barney Cordoba wrote:
> it needs a lot
oled traffic, but it's better than FEC. I have
patched to made
the FreeBSD LAGG/LACP code a little more reliable in this area, and I'll be
posting
those patching in the coming few days.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ooglecode somewhere.
>
> It does what you describe, uses regex to match payload.
Hi,
Our custom code is held here: https://rcs.pfsense.org/projects/pfsense-tools
Simply check out the tools repo and inside pfPorts/ you will find all
our goodies including ipfw-cl
> "whenever my desktop PC"
>
> Now this is where u FAIL. Use dubuntu or windows7 on desktop not FBSD
> and don't try again.
>
> Jax
Perhaps I wasn't clear. The desktop PC (which runs WinXP) is connected directly
to the em0 port on my FreeBSD server. No Ethernet switch in-between.
I connect it
Under 8.0-RELEASE I would get warnings from em(4) in /var/log/messages about
"watchdog timeouts" on em0 whenever my desktop PC connected to em0 was powered
off. This was fine, except for the annoying warnings.
Under 8.1-RELEASE I no longer get the warnings, and any time my desktop is
powered o
x:xx
>bce1: [ITHREAD]
>bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W
>(0x03050C05); Flags( MFW MSI )
>
>
>> can you also send me a lspci and lspci -v ?
>>
>Sorry, this is FreeBSD, not Linux ;-)
>
Try
s great!
http://cvs.pfsense.com/~sullrich/ipsec-tools-devel.zip ... This is a
port file of a recent ipsec-tools cvs checkout + a few patches
provided by vanhu@, extract to /usr/ports/security/ and make install.
The NATT patch is slated to hit the FreeBSD tree soon so please do
report back your findings.
ich/ppp.conf
http://cvs.pfsense.com/~sullrich/mpd.conf
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On Tue, Apr 28, 2009 at 1:28 PM, Bjoern A. Zeeb
wrote:
> On Tue, 28 Apr 2009, Scott Ullrich wrote:
[snip]
> I have NAT-T on top of that. And I am currently doing the whatever
> you'll call it 'final pass', will send it back to Yvan once I am done
> with the last 2
ecently whipped the pfSense's NATT patch into shape:
http://cvs.pfsense.com/~sullrich/NATT.RELENG_8.diff
I am not sure if this is how Yvan wants to solve it for the long term
but it does seem to work OK for the short term until the patch is
brought up to speed.
Scott
___
Thanks for maintaing the patch so far,
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
uple
hours ago and it seems to break all outgoing UDP traffic (DNS
included).
Has anyone else experienced this issue? Backing the patch out of our
pfSense patch roster cleared up the problem.
Is there a newer patch available by chance?
Thanks,
Scott
___
f
I'll bite.
Scott
On Wed, 1 Oct 2008, Jack Vogel wrote:
Jeff Roberson uncovered an issue that might be behind any number of
possible problems.
Our newer hardware (meaning those supported by the igb and ixgbe
drivers) overwrites the buffer address in the RX
descriptor with a variety of
ation is a Dell Inspiron XPS with a Broadcom BCM5705
A1 adaptor, ASIC rev. 0x3001, (bge driver) for 10/100/1000 Mb/s connected to a
Comcast/RCA cable modem at 100 Mb/s.
Thanks in advance for any information you may have.
Scott Bennett, Comm
On 8/21/08, Julian Elischer <[EMAIL PROTECTED]> wrote:
>
> Does anyone know whether the above mentionned bsd systems boot to a ram
> disk or keep their filesystem on teh flash/disk?
pfSense keeps the filesystem and m0n0wall runs out of a memory backed system.
Hope thi
On Wed, Jun 25, 2008 at 4:24 PM, Julian Elischer <[EMAIL PROTECTED]> wrote:
> do you have the ability to test this?
Absolutely. Is this the only thing from preventing it being merged into HEAD?
Scott
___
freebsd-net@freebsd.org mailing
On Wed, Jun 25, 2008 at 3:53 PM, Bjoern A. Zeeb
<[EMAIL PROTECTED]> wrote:
> if it would be that easy, it would have happened 2 years ago.
What can we as a community do to assist in making this easier and doable?
Scott
___
freebsd-net@fr
3-19.diff
might be semi up to date.
Thanks a million for assisting Julian, this is going to make a lot of
folks happy! :)
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ent-type=text%2Fplain
Thanks Julian!
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
hing every time we
move to a newer FreeBSD revision.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 6/3/08, Jon Otterholm <[EMAIL PROTECTED]> wrote:
> Hi.
>
> Are there any plans to implement option carpdev to carp in FreeBSD?
>
> //Jon
See the freebsd-pf archives. Max has a patch ready for testing and
needs more wide-s
afternoon :)
Is it still true that support for the 575 moved from em to igb? If so,
please put an entry in src/UPDATING about it and ask the re/docs team to
make sure it's documented in the next release notes.
Scott
___
freebsd-net@freebsd.org ma
and you just saved me a lot of time :)
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ns or
links that could be helpful?
I also thought i could just use packet marks, but I am just unaware of
anything else to make the pf packets more dynamic... i guess that would be
the goal of this post
--
Lyle Scott, III
http://www.lylescott.ws
___
fr
security/ipsec-tools/work/ipsec-tools-0.7/src.
*** Error code 1
Stop in /usr/ports/security/ipsec-tools/work/ipsec-tools-0.7.
*** Error code 1
Stop in /usr/ports/security/ipsec-tools/work/ipsec-tools-0.7.
*** Error code 1
Stop in /usr/ports/security/ipsec-tools.
**
;make
buildword' but when i do a 'make buildkernel' it says the option is not
found.
Did i do something wrong or what?
--
Lyle Scott, III
http://www.lylescott.ws
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
urs of uptime before the problem becomes
noticeable. If vnodes are never truly getting cleaned, or never getting
their flags cleared so that this loop knows that they are clean, then
it's feasible that they'll accumulate over time, keep on getting flushed
On 11/15/07, Jack Vogel <[EMAIL PROTECTED]> wrote:
> Its IN the chipset, so if its AMD based you won't have it :)
Thanks for the clarification. I'll be sure to buy all Intel parts on
the next server :)
Scott
___
freebsd-net@freeb
ng
on a heavily loaded firewall.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t sure what em(4) cards support it. So I think hardware should
> be available now. At the time the PE29XX family BIOS did not support it
I have a stack of Dell 2970's with Intel 1000 cards and will be happy
to test this when a patch is available. Thanks f
in private...
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e, depending on your perspective)
examples of this in FreeBSD. My vote is to nip the madness in the bud
on if_em and have two (or more drivers) that support their hardware
families well instead of one driver that supports multiple families
marginally.
Scott
Hans Petter Selasky wrote:
Hi Scott,
The discussion has been moved to "[EMAIL PROTECTED]". Please only reply
there next time.
On Wednesday 26 September 2007, Scott Long wrote:
Hans Petter Selasky wrote:
Hi,
Please keep me CC'ed, hence I'm not on all these list
oint of having architecture portable drivers.
John-Mark describes this further. It also makes little sense to push
the responsibility for handling bounce buffers out of a central
subsystem and back into every driver.
Scott
___
freebsd-net@freebsd.org mailing
On 9/24/07, Christopher Cowart <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 18, 2007 at 03:58:16PM -0400, Scott Ullrich wrote:
> How are you detecting when racoon gets wedged? I'd like to replicate
> that on our systems.
Our script is primitive at best but does seem to d
On Tue, 11 Sep 2007 15:46:56 +0200 Volker <[EMAIL PROTECTED]> wrote
>On 09/10/07 23:16, Scott Bennett wrote:
>> Oh. So now I have another couple of white elephants. Damn. And I
>> still
>> don't have anything that will work as a second interface. Si
On Mon, 10 Sep 2007 09:36:14 +0100 Tom Judge <[EMAIL PROTECTED]> wrote:
>Scott Bennett wrote:
>>
>> My Dell Inspiron XPS has just one built-in Ethernet port, and I need to
>> have at least one other. Armed with a printed copy of Section 3.2 of the
>>
:15 hellas kernel: ugen0: detached
Is the Linksys USB200M supported or not? What am I missing here?
Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet: bennett at
probably a bad idea for anything more
than a proof-of-concept. From a cleanliness point of view, making the
software vlan module aware of this as a hardware offload capability and
able to control it via new ioctls sounds more reasonable.
Scott
ks again for your help, George, we appreciate it!
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
; But the reported problem really has similar symptoms.
Thank you Yvan and George!
The PR has been filed and the ID# is
kern/115651
I have added some interesting notes that seem to affect NetBSD as well.
We will be happy to work with anyone to get this s
ll script that looks for racoon
falling over and simply restarting it.
Does anyone know if this is fixed in 7-CURRENT? If so we can easily
wait until 7 arrives as we plan on releasing pfSense on the 7 platform
as soon as it is released.
Georg
we can debug further?
Thanks
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 8/17/07, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Hello!
>
> We are trying to track down a problem that involves a large number of
> ipsec tunnels (in this case 80). Frequently racoon (ipsec-tools
> 0.7rc1 and also 0.6) will deadlock into the sbwait state or will ent
On Wed, 18 Jul 2007 20:48:21 +0100 (BST) Robert Watson
<[EMAIL PROTECTED]> wrote:
>On Wed, 18 Jul 2007, Scott Bennett wrote:
>
>> [Cc: list trimmed a bit more --SB]
>> On Tue, 17 Jul 2007 23:42:14 +0200 Max Laier <[EMAIL PROTECTED]>
>>
>
as been kldload-ed). In
FreeBSD 6.2, AIO results in a warning message at boot time that says
AIO is not MPSAFE and that therefore the networking stack will take a
deep performance hit.
Scott Bennett, Comm. ASMELG, CFIAG
Mike Tancsa wrote:
At 12:50 PM 11/13/2006, Ivan Voras wrote:
Mike Tancsa wrote:
> At 12:15 AM 11/13/2006, Scott Long wrote:
>
>> Is this with EM_INTR_FAST enabled also?
>
> Yes. Havent done the stock case yet, but will do so later today.
Do you have a comparison with Li
Mike Tancsa wrote:
At 12:15 AM 11/13/2006, Scott Long wrote:
Is this with EM_INTR_FAST enabled also?
Without it, the 2 streams are definitely lossy on the management interface
---Mike
Ok, and would you be able to test the polling options as well?
Scott
Mike Tancsa wrote:
At 11:05 PM 11/12/2006, Scott Long wrote:
Mike Tancsa wrote:
However, if I turn on fastforwarding, its back to the old behavior
with it locking up. This was with the stock driver. I will try the
same test with
#define EM_FAST_INTR 1
as well as taking out the nfs option
?
---Mike
Would you mind going so far as to adding NO_ADAPTIVE_MUTEXES? This is
excellent data, thanks a lot for working on it.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
Mike Tancsa wrote:
At 11:41 AM 11/12/2006, Scott Long wrote:
Mike Tancsa wrote:
At 01:42 AM 11/11/2006, Scott Long wrote:
driver. What will help me is if you can hook up a serial console to
your machine and see if it can be made to drop to the debugger while it
is under load and otherwise
Mike Tancsa wrote:
At 01:42 AM 11/11/2006, Scott Long wrote:
driver. What will help me is if you can hook up a serial console to
your machine and see if it can be made to drop to the debugger while it
is under load and otherwise unresponsive. If you can, getting a process
dump might help
nvolve improvements in the FFWD and PFIL_HOOKS code as well as the
driver. What will help me is if you can hook up a serial console to
your machine and see if it can be made to drop to the debugger while it
is under load and otherwise unresponsive. If you can, getting a process
d
ny packets at all
for Gleb, but they expose the system to risk if there is ever an
accidental (or malicious) RX flood on the interface.
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, sen
I tried to setup something exactly like you did. I could do it fine with
freebsd boxes as I would do it via username not ip. Never really got the
problem sorted for windows though. I ended up using openVPN instead. I
would seriously recommend you try this solution as its far easier to
setup. Be
ses problems, three minutes later it will
turn back off automatically.
Unfortunately, the machine dropped off the network immediately and is not
coming back. I'll get to its console on Monday, but something is still very
wrong with the em-driver :-(
-mi
So the driver
Jack Vogel wrote:
On 10/25/06, Scott Long <[EMAIL PROTECTED]> wrote:
Jack Vogel wrote:
> On 10/25/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote:
>
>> 3) In em_process_receive_interrupts/em_rxeof always decrement
>> the count on every run th
Jack Vogel wrote:
On 10/25/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote:
3) In em_process_receive_interrupts/em_rxeof always decrement
the count on every run through the loop. If you notice
count is an is an int that starts at the passed in value
of -1. It then cou
Doug Ambrisko wrote:
John Polstra writes:
| On 19-Oct-2006 Scott Long wrote:
| > The performance measurements that Andre and I did early this year showed
| > that the INTR_FAST handler provided a very large benefit.
|
| I'm trying to understand why that's the case.
Bruce Evans wrote:
On Thu, 19 Oct 2006, John Polstra wrote:
On 19-Oct-2006 Scott Long wrote:
The performance measurements that Andre and I did early this year showed
that the INTR_FAST handler provided a very large benefit.
I'm trying to understand why that's the case. Is it
John Polstra wrote:
On 19-Oct-2006 Scott Long wrote:
The performance measurements that Andre and I did early this year showed
that the INTR_FAST handler provided a very large benefit.
I'm trying to understand why that's the case. Is it because an
INTR_FAST interrupt doesn't ha
Bruce Evans wrote:
On Thu, 19 Oct 2006, Scott Long wrote:
Bruce Evans wrote:
On Wed, 18 Oct 2006, Kris Kennaway wrote:
I have been working with someone's system that has em shared with
fxp,
and a simple fetch over the em (e.g. of a 10 GB file of zeroes) is
enough to produce wat
Bruce Evans wrote:
On Wed, 18 Oct 2006, Scott Long wrote:
[too much quoted; much deleted]
Bruce Evans wrote:
On Wed, 18 Oct 2006, Kris Kennaway wrote:
I have been working with someone's system that has em shared with fxp,
and a simple fetch over the em (e.g. of a 10 GB file of zeroe
oblem you pointed out with the cached copy of the interrupt status
possibly going stale is a calculated risk. If a new condition happens,
the chip will continue to signal an interrupt until it is handled. That
will generate an interrupt on the CPU after the taskqueue calls
em_enable_intr(), in which
1 - 100 of 163 matches
Mail list logo
