> -Original Message-
> From: Stefan Hajnoczi
> Sent: Thursday, July 16, 2015 23:59
> On Mon, Jul 06, 2015 at 07:39:35AM -0700, Dexuan Cui wrote:
> > Hyper-V VM Sockets (hvsock) is a byte-stream based communication
> mechanism
> > between Windowsd 10 (or later) host and a guest. It's kind of
From: Shaohui Xie
Teranetics TN2020 is compliant with IEEE 802.3an 10 Gigabit.
Signed-off-by: Shaohui Xie
---
drivers/net/phy/Kconfig | 5 ++
drivers/net/phy/Makefile | 1 +
drivers/net/phy/teranetics.c | 128 +++
3 files changed, 134 insert
On 7/16/15, 1:04 AM, sfel...@gmail.com wrote:
From: Scott Feldman
Just before queuing skb for xmit on port, check if skb has been marked by
switchdev port driver as already fordwarded by device. If so, drop skb. A
non-zero skb->offload_fwd_mark field is set by the switchdev port
driver/device
Let eBPF programs call skb_vlan_push/pop via helpers.
JIT changes to accomodate of re-caching of skb->data and headerlen
turned out to be pretty simple.
This patch is on top of Daniel's bpf_get_cgroup_classid():
http://patchwork.ozlabs.org/patch/495826/
to avoid merge conflicts.
Alexei Starovoito
In order to let eBPF programs call skb_vlan_push/pop via helper functions
eBPF JITs need to recognize helpers that change skb->data, since
skb->data and hlen are cached as part of JIT code generation.
- arm64 JIT is using bpf_load_pointer() without caching, so it's ok as-is.
- x64 JIT recognizes bp
improve accuracy of timing in test_bpf and add two stress tests:
- {skb->data[0], get_smp_processor_id} repeated 2k times
- {skb->data[0], vlan_push} x 68 followed by {skb->data[0], vlan_pop} x 68
1st test is useful to test performance of JIT implementation of BPF_LD_ABS
together with BPF_CALL ins
On Thu, Jul 16, 2015 at 12:58:45PM +0200, Wolfgang Walter wrote:
> Am Donnerstag, 16. Juli 2015, 08:23:50 schrieb Herbert Xu:
> > On Wed, Jul 15, 2015 at 02:25:59PM +0200, Wolfgang Walter wrote:
> > > Yes. Switching TSO off and leaving GRO on works, too.
> >
> > OK, could you please try this patch
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/bridge/br_mdb.c
between commit:
5ebc784625ea ("bridge: mdb: fix double add notification")
from the net tree and commit:
09cf0211f970 ("bridge: mdb: fill state in br_mdb_notify")
from the net-next tree.
I fixe
We receoved a bug report from someone using vmware:
WARNING: CPU: 3 PID: 660 at kernel/sched/core.c:7389
__might_sleep+0x7d/0x90()
do not call blocking ops when !TASK_RUNNING; state=1 set at
[] prepare_to_wait+0x2d/0x90
Modules linked in: vmw_vsock_vmci_transport vsock snd_seq_midi
snd_seq_midi_e
On 16/07/15 07:50, Stas Sergeev wrote:
>
> Currently fixed_phy driver recognizes only the link-up state.
> This simple patch adds an implementation of link-down state.
> It fixes the status registers when link is down, and also allows
> to register the fixed-phy with link down without specifying t
Now that we have reworked the way we perform the PHY initialization, we
no longer need to differentiate between init time vs. non-init time
calls, just use a dev_info_once() print to print the PHY type.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/broadcom/genet/bcmgenet.c | 2 +-
dr
We are currently doing a full PHY initialization and even starting the
pHY state machine during bcmgenet_mii_init() which is executed in the
driver's probe function. This is convenient to determine whether we can
attach to a proper PHY device but comes at the expense of spending up to
10ms per MDIO
bcmgenet_open()'s error path call free_irq() with a dev_id argument
different from the one we used to call request_irq() with, this will
make us trip over the warning in kernel/irq/manage.c:__free_irq()
Fixes: 1c1008c793fa4 ("net: bcmgenet: add main driver file")
Signed-off-by: Florian Fainelli
-
We are currently issuing multiple PHY resets during a suspend/resume,
first during bcmgenet_power_up() which does a hardware reset, then a
software reset by calling bcmgenet_mii_reset(). This is both unnecessary
and can take as long as 10ms per MDIO transactions while we re-apply
workarounds becaus
Hi David, Petri, Jaedon,
This patch series reworks how we perform PHY initialization and resets in the
GENET driver. Although this contains mostly fixes, some of the changes are a
bit too intrusive to be backported to 'net' at the moment.
Some of the motivations behind these changes were to reduc
We are currently disabling the GPHY interface during bcmgenet_close(),
and attempting to power it back on during bcmgenet_open(). This works
fine for the first time, because we called bcmgenet_mii_config() which
took care of enabling the interface, however, bcmgenet_power_up() really
needs to power
Our internal GPHY might be powered off before we attempt scanning the
MDIO bus and bind a driver to it. The way we are currently determining
whether a PHY is internal or not is done *after* we have successfully
matched its driver. If the PHY is powered down, it will not respond to
the MDIO bus, so
Refactor code to clearly separate probing non-dt versus dt. In the
non-dt case platform data must be supplied to probe successfully.
For dt the platform data structure is created and match data is
copied into it. Note that support for supplying platform data in
dt from AUXDATA is dropped as no user
Export stmmac_probe_config_dt() and stmmac_get_platform_resources()
so they can be used in the dwmac-* drivers themselves. This will
allow us to build more flexible and standalone drivers which just
use stmmac_platform as a library for setup functions.
Signed-off-by: Joachim Eastwood
---
drivers
By using of_device_get_match_data() the code that retrieve
match data can be simplified quite a bit.
Signed-off-by: Joachim Eastwood
---
drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet/stmicro/
Refactor all code that deals with platform resources into it's
own get function. This function will later be used in the probe
function in dwmac-* drivers.
Signed-off-by: Joachim Eastwood
---
.../net/ethernet/stmicro/stmmac/stmmac_platform.c | 64 +-
1 file changed, 37 inser
By using a few functions from stmmac_platform we can now create
a proper probe function in this driver. By doing so we can drop
the OF match data and simplify the overall driver.
Signed-off-by: Joachim Eastwood
---
drivers/net/ethernet/stmicro/stmmac/dwmac-meson.c | 31 +++
1
Hi everyone,
This patch set continues the conversion of the dwmac glue layers
to more proper platform drivers. The first part of the patch set
cleans up stmmac_platform a bit. Refactors code from the common
probe function and exports two functions that will be used in
the dwmac-* drivers.
Second
By using a few functions from stmmac_platform we can now create
a proper probe function in this driver. By doing so we can drop
the OF match data and simplify the overall driver.
Signed-off-by: Joachim Eastwood
---
.../net/ethernet/stmicro/stmmac/dwmac-lpc18xx.c| 59 +-
1
Both of these fields are unused and has been unused since they
were added 3 and 5 years ago. Drop them since they are clearly
not very useful.
Signed-off-by: Joachim Eastwood
---
Documentation/networking/stmmac.txt | 4
include/linux/stmmac.h | 2 --
2 files changed, 6 deletion
Since stmmac_probe_config_dt() allocates the platform data structure
it is cleaner if it just returned this structure directly. This
function will later be used in the probe function in dwmac-* drivers.
Signed-off-by: Joachim Eastwood
---
.../net/ethernet/stmicro/stmmac/stmmac_platform.c | 28 +
(Repost because old post seems to be lost.)
This patch adds a driver for LAN7800 family of
USB 2.0 & USB 3.0 to Gigabit Ethernet.
Signed-off-by: Woojung Huh
---
drivers/net/usb/Kconfig | 10 +
drivers/net/usb/Makefile |1 +
drivers/net/usb/lan78xx.c | 3596 +
On Thu, 2015-07-16 at 22:18 +0200, Bjørn Mork wrote:
> I'm on vacation without any usable Internet or other code access, so you'll
> have to excuse me if I'm missing something. But this seems to leave
> union_desc uninitialized, doesn't it?
Yes, good catch. I'll make a new version.
Tha
Corcodel Marian :
> Set bits on register Interrupt status on limits by
> configuration(critical).
> On chips not alls bits is in use and some is reserved this patch solve
> this issue.
Did you experience a real bug or is it a theoretical issue ?
I don't mind experimental stuff provided:
- it's t
On Thu, Jul 16, 2015 at 7:52 AM, Thomas Graf wrote:
> On 07/16/15 at 05:59pm, Simon Horman wrote:
>> On Fri, Jul 10, 2015 at 04:19:24PM +0200, Thomas Graf wrote:
>> > static void ipgre_tap_setup(struct net_device *dev)
>> > {
>> > ether_setup(dev);
>> > - dev->netdev_ops = &gre_tap
The TCCR.TSRQn bit may get clearead after TCCR gets read, so that TCCR write
would get skipped. We don't need to check this bit before setting.
Signed-off-by: Sergei Shtylyov
---
The patch is against Dave Miller's 'net.git' repo plus the patch I sent on
Tuesday.
drivers/net/ethernet/renesas/ra
Sierra Wireless MC7305/MC7355 with USB ID 1199:9041 also provide a
second QMI/network interface like the MC73xx with USB ID 1199:68c0 on
USB interface #10 when used in the appropriate USB configuration.
Add the corresponding QMI_FIXED_INTF entry to the qmi_wwan driver.
Please note that the second
In our effort to move control of the links to the link aggregation
layer, we move the perodic link supervision timer to struct tipc_node.
The new timer is shared between all links belonging to the node, thus
saving resources, while still kicking the FSM on both its pertaining
links at each expirati
As a step towards turning links into node internal entities, we move the
creation of links from the neighbor discovery logics to the node's link
control logics.
We also create an additional entry for the link's media address in the
newly introduced struct tipc_link_entry, since this is where it is
We create a second, simpler, link timer function, tipc_link_timeout().
The new function makes use of the new FSM function introduced in the
previous commit, and just like it, takes a buffer queue as parameter.
It returns an event bit field and potentially a link protocol packet
to the caller.
The
struct tipc_node currently holds two arrays of link pointers; one,
indexed by bearer identity, which contains all links irrespective of
current state, and one two-slot array for the currently active link
or links. The latter array contains direct pointers into the elements
of the former. This has t
The status flag LINK_STOPPED is not needed any more, since the
mechanism for delayed deletion of links has been removed.
Likewise, LINK_STARTED and LINK_START_EVT are unnecessary,
because we can just as well start the link timer directly from
inside tipc_link_create().
We eliminate these flags in
The link FSM implementation is currently unnecessarily complex.
It sometimes checks for conditional state outside the FSM data
before deciding next state, and often performs actions directly
inside the FSM logics.
In this commit, we create a second, simpler FSM implementation,
that as far as possi
struct 'tipc_node' currently contains two arrays for link attributes,
one for the link pointers, and one for the usable link MTUs.
We now group those into a new struct 'tipc_link_entry', and intoduce
one single array consisting of such enties. Apart from being a cosmetic
improvement, this is a sta
We convert packet/message reception according to the same principle
we have been using for message sending and timeout handling:
We move the function tipc_rcv() to node.c, hence handling the initial
packet reception at the link aggregation level. The function grabs
the node lock, selects the recei
When the function tipc_link_xmit() is given a buffer list for
transmission, it currently consumes the list both when transmission
is successful and when it fails, except for the special case when
it encounters link congestion.
This behavior is inconsistent, and needs to be corrected if we want
to
The logics for determining when a node is permitted to establish
and maintain contact with its peer node becomes non-trivial in the
presence of multiple parallel links that may come and go independently.
A known failure scenario is that one endpoint registers both its links
to the peer lost, clean
At present, the link input queue and the name distributor receive
queues are fields aggregated in struct tipc_link. This is a hazard,
because a link might be deleted while a receiving socket still keeps
reference to one of the queues.
This commit fixes this bug. However, rather than adding yet ano
This is the first batch of a longer series that has two main objectives:
o Finer lock granularity during message sending and reception,
especially regarding usage of the node spinlock.
o Better separation between the link layer implementation and the link
aggregation layer, represented by nod
As a preparation for later changes, we introduce a new function
tipc_link_build_proto_msg(). Instead of actually sending the created
protocol message, it only creates it and adds it to the head of a
skb queue provided by the caller.
Since we still need the existing function tipc_link_protocol_xmit
Currently, message sending is performed through a deep call chain,
where the node spinlock is grabbed and held during a significant
part of the transmission time. This is clearly detrimental to
overall throughput performance; it would be better if we could send
the message after the spinlock has be
I'm on vacation without any usable Internet or other code access, so you'll
have to excuse me if I'm missing something. But this seems to leave union_desc
uninitialized, doesn't it?
Bjørn
On July 16, 2015 9:24:34 PM CEST, Oliver Neukum wrote:
>Switch to the common parser
>
>Signed-off-by: Oli
It's not used anywhere.
Signed-off-by: Jiri Benc
---
include/linux/skbuff.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index d6cdd6e87d53..a5395be9fe7b 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -2671,12 +2671
On 16/07/15 12:34, Nicholas Krause wrote:
> This makes the function bcmgenet_power_down return the variable ret
> rather then zero in order to make this function be able to signal its
> caller with a error code when a failure occurs internally rather then
> always appearing to run successfully to i
The keystone qmss will raise interrupt when packet arrive at the
receive queue. Only control available to avoid interrupt from happening
is to keep the free descriptor queue (FDQ) empty in the receive side.
So the filling of descriptors into the FDQ has to happen after
request_irq() call is made as
On 14/07/15 12:37, Florian Fainelli wrote:
> We are currently issuing multiple PHY resets during a suspend/resume,
> first during bcmgenet_power_up() which does a hardware reset, then a
> software reset by calling bcmgenet_mii_reset(). This is both unnecessary
> and can take as long as 10ms per MDI
On 15/07/15 08:09, Nicholas Krause wrote:
> This makes the function bcmgenet_power_down return the variable ret
> rather then zero in order to make this function be able to signal its
> caller with a error code when a failure occurs internally rather then
> always appearing to run successfully to i
On Thu, 2015-07-16 at 11:17 -0700, David Miller wrote:
> From: Tom Herbert
> Date: Thu, 16 Jul 2015 08:43:25 -0700
>
> > On Thu, Jul 16, 2015 at 5:40 AM, Denys Vlasenko wrote:
> >> This patch deinlines jhash, jhash2 and __jhash_nwords.
> >>
> >> It also removes rhashtable_jhash2(key, length, see
On Thu, 2015-07-16 at 12:18 -0700, Michael Chan wrote:
> On Thu, 2015-07-16 at 14:51 -0400, Nicholas Krause wrote:
> > This adds proper error handling for if the calls to the function
> > tg3_phy_lpbk_set fail by returning -EIO by assigning the return
> > value to the variable err and if it equal
On Thu, 2015-07-16 at 14:51 -0400, Nicholas Krause wrote:
> This adds proper error handling for if the calls to the function
> tg3_phy_lpbk_set fail by returning -EIO by assigning the return
> value to the variable err and if it equals anything other then
> zero jumps to the goto label done as no
On Thu, Jul 16, 2015 at 12:01:55PM +, Liran Liss wrote:
> - Name space lookup is done based on BTH.pkey, private_data.IP, and
> optionally GRH.DGID (if present, for extra validation)
Just changing the pkey to BTH.pkey would be fine by me.
Using GRH.DGID if available instead of the primary
From: Tom Herbert
Date: Thu, 16 Jul 2015 08:43:25 -0700
> On Thu, Jul 16, 2015 at 5:40 AM, Denys Vlasenko wrote:
>> This patch deinlines jhash, jhash2 and __jhash_nwords.
>>
>> It also removes rhashtable_jhash2(key, length, seed)
>> because it was merely calling jhash2(key, length, seed).
>>
>>
The current code returns from probe without waiting for the proper handling
of subchannels that may be requested. If the netvsc driver were to be rapidly
loaded/unloaded, we can trigger a panic as the unload will be tearing
down state that may not have been fully setup yet. We fix this issue by ma
On 7/16/15 9:46 AM, Nicolas Schichan wrote:
This serie fixes issues with the ARM BPF JIT and adds support for more
instructions to the ARM BPF JIT.
The first three patches are fixing bugs in the ARM JIT and should
probably find their way to a stable kernel.
The last three patches add support to
On 16/07/15 03:18, Corcodel Marian wrote:
>
> Set bits on register Interrupt status on limits by
> configuration(critical).
> On chips not alls bits is in use and some is reserved this patch solve this
> issue.
>
> Committer: Corcodel Marian
> Changes to be committed:
> modified: dr
Previously, the JIT would reject negative offsets known during code
generation and mishandle negative offsets provided at runtime.
Fix that by calling bpf_internal_load_pointer_neg_helper()
appropriately in the jit_get_skb_{b,h,w} slow path helpers and by forcing
the execution flow to the slow pat
To check whether the load should take the fast path or not, the code
would check that (r_skb_hlen - load_order) is greater than the offset
of the access using an "Unsigned higher or same" condition. For
halfword accesses and an skb length of 1 at offset 0, that test is
valid, as we end up comparing
Hello,
This serie fixes issues with the ARM BPF JIT and adds support for more
instructions to the ARM BPF JIT.
The first three patches are fixing bugs in the ARM JIT and should
probably find their way to a stable kernel.
The last three patches add support to the ARM JIT for more BPF
instructions
This makes BPF_ANC | SKF_AD_VLAN_TAG and BPF_ANC | SKF_AD_VLAN_TAG_PRESENT
have the same behaviour as the in kernel VM and makes the test_bpf LD_VLAN_TAG
and LD_VLAN_TAG_PRESENT tests pass.
Signed-off-by: Nicolas Schichan
---
arch/arm/net/bpf_jit_32.c | 8 +---
1 file changed, 5 insertions(+
Signed-off-by: Nicolas Schichan
---
arch/arm/net/bpf_jit_32.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/net/bpf_jit_32.c b/arch/arm/net/bpf_jit_32.c
index 6ff248c..3c73caf 100644
--- a/arch/arm/net/bpf_jit_32.c
+++ b/arch/arm/net/bpf_jit_32.c
@@ -915,6 +915,14 @@ b_epil
Signed-off-by: Nicolas Schichan
---
arch/arm/net/bpf_jit_32.c | 22 --
arch/arm/net/bpf_jit_32.h | 3 +++
2 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/arch/arm/net/bpf_jit_32.c b/arch/arm/net/bpf_jit_32.c
index 3c73caf..876060b 100644
--- a/arch/arm/net/bpf
Signed-off-by: Nicolas Schichan
---
arch/arm/net/bpf_jit_32.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/net/bpf_jit_32.c b/arch/arm/net/bpf_jit_32.c
index c011e22..6ff248c 100644
--- a/arch/arm/net/bpf_jit_32.c
+++ b/arch/arm/net/bpf_jit_32.c
@@ -895,6 +895,17 @@ b
On Thu, Jul 16, 2015 at 10:50:59AM -0300, Marcelo Ricardo Leitner wrote:
> On Tue, Jul 14, 2015 at 02:23:11PM +0200, Michal Kubecek wrote:
> > @@ -278,6 +292,14 @@ static int sctp_new_state(enum ip_conntrack_dir dir,
> > pr_debug("SCTP_CID_SHUTDOWN_COMPLETE\n");
> > i = 8;
>
On Mon, Jul 06, 2015 at 07:39:35AM -0700, Dexuan Cui wrote:
> Hyper-V VM Sockets (hvsock) is a byte-stream based communication mechanism
> between Windowsd 10 (or later) host and a guest. It's kind of TCP over
> VMBus, but the transportation layer (VMBus) is much simpler than IP.
> With Hyper-V VM
On Thu, Jul 16, 2015 at 5:40 AM, Denys Vlasenko wrote:
> This patch deinlines jhash, jhash2 and __jhash_nwords.
>
> It also removes rhashtable_jhash2(key, length, seed)
> because it was merely calling jhash2(key, length, seed).
>
> With this .config: http://busybox.net/~vda/kernel_config,
> after
On Thu, Jul 16, 2015 at 10:10:43AM +0300, Yuval Mintz wrote:
> The new FW will allow us to utilize some new features in our driver,
> mainly adding vlan stripping offload and vxlan offload support.
>
> In addition, this fixes several issues:
> - Packets from a VF with pvid configured which were s
On Thu, Jul 16, 2015 at 1:33 PM, Hiroshi Shimamoto
wrote:
> From: Hiroshi Shimamoto
>
> Add netlink directives and ndo entry to trust VF user.
You haven't posted cover letter stating the V7 --> V6 and V6 --> older
versions changes
Or.
> This controls the special permission of VF user.
> The a
The commit 898b2970e2c9 ("mvneta: implement SGMII-based in-band link state
signaling") implemented the link parameters auto-negotiation unconditionally.
Unfortunately it appears that some HW that implements SGMII protocol,
doesn't generate the inband status, so it is not possible to auto-negotiate
Currently the PHY management type is selected by the MAC driver arbitrary.
The decision is based on the presence of the "fixed-link" node and on a
will of the driver's authors.
This caused a regression recently, when mvneta driver suddenly started
to use the in-band status for auto-negotiation on
On 07/16/15 at 05:59pm, Simon Horman wrote:
> On Fri, Jul 10, 2015 at 04:19:24PM +0200, Thomas Graf wrote:
> > static void ipgre_tap_setup(struct net_device *dev)
> > {
> > ether_setup(dev);
> > - dev->netdev_ops = &gre_tap_netdev_ops;
> > dev->priv_flags |= IFF_LIVE_ADD
Currently fixed_phy driver recognizes only the link-up state.
This simple patch adds an implementation of link-down state.
It fixes the status registers when link is down, and also allows
to register the fixed-phy with link down without specifying the speed.
Signed-off-by: Stas Sergeev
CC: Flor
Hello.
Currently the link status auto-negotiation is enabled
for any SGMII link with fixed-link DT binding.
The regression was reported:
https://lkml.org/lkml/2015/7/8/865
Apparently not all HW that implements SGMII protocol, generates the
inband status for the auto-negotiation to work.
More detai
On 15-07-16 01:14 AM, Jiri Pirko wrote:
> Thu, Jul 16, 2015 at 09:09:39AM CEST, sfel...@gmail.com wrote:
>> On Wed, Jul 15, 2015 at 11:58 PM, Jiri Pirko wrote:
>>> Thu, Jul 16, 2015 at 08:40:31AM CEST, sfel...@gmail.com wrote:
On Wed, Jul 15, 2015 at 6:39 PM, Simon Horman
wrote:
> T
On 07/16/2015 05:40 AM, Denys Vlasenko wrote:
This patch deinlines jhash, jhash2 and __jhash_nwords.
It also removes rhashtable_jhash2(key, length, seed)
because it was merely calling jhash2(key, length, seed).
With this .config: http://busybox.net/~vda/kernel_config,
after deinlining these fun
On Thu, Jul 16, 2015 at 09:09:57AM -0400, Vlad Yasevich wrote:
> On 07/15/2015 03:03 PM, Marcelo Ricardo Leitner wrote:
> > On Fri, Jul 10, 2015 at 03:27:02PM -0300, Marcelo Ricardo Leitner wrote:
> >> On Fri, Jul 10, 2015 at 01:14:21PM -0400, Vlad Yasevich wrote:
> >>> On 07/10/2015 12:17 PM, Marc
On Thu, Jul 16, 2015 at 09:50:16AM -0400, Vlad Yasevich wrote:
> On 07/14/2015 01:13 PM, Marcelo Ricardo Leitner wrote:
> > SCTP has this operation to peel off associations from a given socket and
> > create a new socket using this association. We currently have two ways
> > to use this operation:
On Tue, Jul 14, 2015 at 02:23:11PM +0200, Michal Kubecek wrote:
> Currently nf_conntrack_proto_sctp module handles only packets between
> primary addresses used to establish the connection. Any packets between
> secondary addresses are classified as invalid so that usual firewall
> configurations d
On 07/14/2015 01:13 PM, Marcelo Ricardo Leitner wrote:
> SCTP has this operation to peel off associations from a given socket and
> create a new socket using this association. We currently have two ways
> to use this operation:
> - via getsockopt(), on which it will also create and return a file
>
On Thu, Jul 16, 2015 at 02:05:12PM +0200, Michal Kubecek wrote:
> On Wed, Jul 15, 2015 at 05:35:08PM -0300, Marcelo Ricardo Leitner wrote:
> > Hi,
> >
> > On Tue, Jul 14, 2015 at 06:42:25PM +0200, Michal Kubecek wrote:
> > > On Tue, Jul 14, 2015 at 03:42:03PM +0200, Florian Westphal wrote:
> > > >
On 07/15/2015 03:03 PM, Marcelo Ricardo Leitner wrote:
> On Fri, Jul 10, 2015 at 03:27:02PM -0300, Marcelo Ricardo Leitner wrote:
>> On Fri, Jul 10, 2015 at 01:14:21PM -0400, Vlad Yasevich wrote:
>>> On 07/10/2015 12:17 PM, Marcelo Ricardo Leitner wrote:
On Fri, Jul 10, 2015 at 11:35:28AM -040
> On July 16, 2015 at 2:48 PM "Motejlek, Petr"
> wrote:
>
> Could you please give me some example of such a tc command that
> would tell me the statistics? I am not sure what you mean.
tc -s qdisc show dev eth0
> Is there a way I can manipulate the internal rbtree queue size, please?
Sure, the
> On July 16, 2015 at 1:28 PM "Motejlek, Petr"
> wrote:
> I was wondering what queues/buffers does netem use and how does one
> control or monitor them?
netem uses his own rbtree based queue. You can use tc(1) to get
statistics.
> I could not find this information anywhere and I am not that goo
Hello Hagen,
Could you please give me some example of such a tc command that would tell me
the statistics? I am not sure what you mean.
Is there a way I can manipulate the internal rbtree queue size, please?
Thank you
Petr MOTEJLEK
From: Hagen Paul Pfei
There is no need to use hex_dump_to_buffer() in the cases like this:
hexdump_to_buffer(buf, len, 16, 1, outbuf, outlen, false); /* len
<= 16 */
sprintf("%s\n", outbuf);
since it maybe easily converted to simple:
sprintf("%*ph\n", len, buf);
Note: it seems in the ca
There is no need to use hex_dump_to_buffer() in the cases like this:
hexdump_to_buffer(buf, len, 16, 1, outbuf, outlen, false); /* len
<= 16 */
sprintf("%s\n", outbuf);
since it maybe easily converted to simple:
sprintf("%*ph\n", len, buf);
Note: it seems in one ca
This patch deinlines jhash, jhash2 and __jhash_nwords.
It also removes rhashtable_jhash2(key, length, seed)
because it was merely calling jhash2(key, length, seed).
With this .config: http://busybox.net/~vda/kernel_config,
after deinlining these functions have sizes and callsite counts
as follows
> From: Jason Gunthorpe [mailto:jguntho...@obsidianresearch.com]
> > After all, it is the payload that designates the entity that you
> > want to establish a connection to, rather than the packet headers,
> > which are just meant to relay the packet to the proper CM
>
> No, that isn't right. The
On 2015/7/16 19:54, Nikolay Aleksandrov wrote:
> On 07/16/2015 01:50 PM, Nikolay Aleksandrov wrote:
>> On 07/16/2015 01:48 PM, Ding Tianhong wrote:
>>> On 2015/7/16 17:24, Nikolay Aleksandrov wrote:
On 07/16/2015 10:30 AM, Ding Tianhong wrote:
> The "follow" fail_over_mac policy is useful
On Wed, Jul 15, 2015 at 05:35:08PM -0300, Marcelo Ricardo Leitner wrote:
> Hi,
>
> On Tue, Jul 14, 2015 at 06:42:25PM +0200, Michal Kubecek wrote:
> > On Tue, Jul 14, 2015 at 03:42:03PM +0200, Florian Westphal wrote:
> > > Michal Kubecek wrote:
> > > > + case SCTP_CID_HEARTBEAT:
> > > > +
On 07/16/2015 01:54 PM, Nikolay Aleksandrov wrote:
> On 07/16/2015 01:50 PM, Nikolay Aleksandrov wrote:
>> On 07/16/2015 01:48 PM, Ding Tianhong wrote:
>>> On 2015/7/16 17:24, Nikolay Aleksandrov wrote:
On 07/16/2015 10:30 AM, Ding Tianhong wrote:
> The "follow" fail_over_mac policy is use
On 07/16/2015 01:50 PM, Nikolay Aleksandrov wrote:
> On 07/16/2015 01:48 PM, Ding Tianhong wrote:
>> On 2015/7/16 17:24, Nikolay Aleksandrov wrote:
>>> On 07/16/2015 10:30 AM, Ding Tianhong wrote:
The "follow" fail_over_mac policy is useful for multiport devices that
either become confuse
On 07/16/2015 01:48 PM, Ding Tianhong wrote:
> On 2015/7/16 17:24, Nikolay Aleksandrov wrote:
>> On 07/16/2015 10:30 AM, Ding Tianhong wrote:
>>> The "follow" fail_over_mac policy is useful for multiport devices that
>>> either become confused or incur a performance penalty when multiple
>>> ports
On 2015/7/16 17:24, Nikolay Aleksandrov wrote:
> On 07/16/2015 10:30 AM, Ding Tianhong wrote:
>> The "follow" fail_over_mac policy is useful for multiport devices that
>> either become confused or incur a performance penalty when multiple
>> ports are programmed with the same MAC address, but the s
Hello,
I was wondering what queues/buffers does netem use and how does one control or
monitor them?
I could not find this information anywhere and I am not that good in reading
the sources to be able to tell enough about this :) If we talk only about the
situation where netem is the root qdisc
> From: David Miller
> Sent: Thursday, July 16, 2015 12:19
>
> From: Dexuan Cui
> Date: Tue, 14 Jul 2015 03:00:48 -0700
>
> > + pr_debug("hvsock_sk_destruct: called\n");
>
> Debug logging just to state that a function is called is not appropriate,
> we have very sophisticated tracing facilitie
1 - 100 of 140 matches
Mail list logo
