similar to: poor performance for building route cache

Displaying 20 results from an estimated 8000 matches similar to: "poor performance for building route cache"

2019 Jan 09
0
[PATCH v5 06/20] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When
2019 Jan 05
0
[PATCH v4 02/16] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When
2015 May 15
0
Back to eth shuffling ...
So a 70-persistent-net.rules like # onboard port 1 -> eth0 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:00:19.0", NAME="eth0" # PCIe card -> eth2 ACTION=="add", SUBSYSTEM=="net", BUS=="pci", ID=="0000:03:00.0", NAME="eth2" # onboard port 2 -> eth1 ACTION=="add",
2015 May 15
0
Back to eth shuffling ...
another identical machine will have the same bus ids. that's why this works. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd GitHub: @tartansandal Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must
2018 Dec 14
0
[WIP PATCH 03/15] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When
2015 May 15
2
Back to eth shuffling ...
Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel
2015 May 15
2
Back to eth shuffling ...
Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at
2015 May 13
2
Back to eth shuffling ...
So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After
2018 Dec 18
0
[WIP PATCH 03/15] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things
2015 May 14
2
Back to eth shuffling ...
When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what "fixed" the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo "[KICKSTART] Binding eth interfaces to the expected MAC address in UDEV" echo "## Created by
2005 Nov 14
0
Xend fails to start on newly compiled xen dom0 kernel
Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent
2020 May 21
2
[Bug 1427] New: can not reuse source port to a DNATed IP if it is being used by another connection
https://bugzilla.netfilter.org/show_bug.cgi?id=1427 Bug ID: 1427 Summary: can not reuse source port to a DNATed IP if it is being used by another connection Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5
2015 May 14
0
Back to eth shuffling ...
On 15 May 2015 at 03:51, Ashley M. Kirchner <ashley at pcraft.com> wrote: > After the machine boots and I look in /root/ksnet-devices, I see the MAC > addresses for the devices as: > Port1 -> eth0 > PCIe Card-> eth1 > Port2 -> eth2 > > And yet, during the machine's POST (which can verify by the PXE boot up of > each device), it correctly enumerates the
2018 Dec 19
1
[WIP PATCH 03/15] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote: > On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > > The current way of handling refcounting in the DP MST helpers is really > > > confusing and probably just plain wrong because it's been hacked up many > > > times over the
2018 Dec 14
2
[WIP PATCH 03/15] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports
On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > The current way of handling refcounting in the DP MST helpers is really > confusing and probably just plain wrong because it's been hacked up many > times over the years without anyone actually going over the code and > seeing if things could be simplified. > > To the best of my understanding, the current scheme
2005 Jun 08
2
General Traffic Control Question
Here''s my situation: I''ve got an Intel machine running a 2.6.9 linux kernel and this box has 4 modems attached to it via a usb to serial port expander. In order to force data down each of the modems, some pretty simple rules are used and they are as follows: iptables -t mangle -A OUTPUT -p tcp --dport $PORT1 -j MARK --set-mark 1 iptables -t mangle -A OUTPUT -p tcp --dport
2008 Mar 02
0
Cisco 7970 - register with NAT phone
continuing discussions of 79xx issues. i've seen referenced and am experiencing difficulty getting a 7970 to work behind NAT to a public asterisk server. i am successful with 7960s. 1. SIP load is 70.8-3-3SR2S 2. config works fine if 7970 is connecting to an asterisk server a local LAN (same subnet) 3. when debugging it in a NAT'd environment I see the register and
2007 Apr 18
0
[Bridge] Problem Bridging VLANs
Hi bridge list: Bart de Schuymer suggested that this question might be better placed on this list rather than in the ebtables area. So here it is : ================================================================= Hi listers: I am a relative Penquin Newcomer, and I am (therefore?) encountering problems trying to setup a simple bridge/firewall between two vlans sharing portions of the same
2011 Feb 04
1
Dovecot 2 multiple address/port binding
Hello, Sorry, I know the topic has been talked about already but I searched the archives and I'm still unsure of the proper way to have dovecot (imap-login) listen to several addresses and/or several ports. 1. how do I translate dovecot-1 protocol imap { listen = xx.xx.xx.xx:143 yy.yy.yy.yy:143 ssl_listen = xx.xx.xx.xx:993 yy.yy.yy.yy:939 } I started by service imap-login {
2011 Feb 03
1
pci-passthrough nic but no link
I hope someone can enlighten me. I have a quad-port Intel 82580 nic (igb driver) on my system and I''d like to dedicate each nic to a HVM via VT-d PCI passthrough. The IOMMU on my system seems to work, I can assign the PCI devices to my HVMs. The HVMs see the pci device and load their respective igb drivers, and ethtool -i eth0 works on each HVM, shows the drivers are loaded and the