On Sun, 28 Feb 2016, Amitoj Kaur Chawla wrote:
On Sun, Feb 28, 2016 at 12:18 AM, Stafford Horne wrote:
>
>
> On Thu, 25 Feb 2016, David Miller wrote:
>
>> From: Amitoj Kaur Chawla
>> Date: Wed, 24 Feb 2016 19:28:19 +0530
>>
>>> Convert a call to init_timer and accompanying intializations of
In commit 5b6490def9168af6a ("3c59x: Use setup_timer()") Amitoj
removed add_timer which sets up the epires timer. In this patch
the behavior is restore but it uses mod_timer which is a bit more
compact.
Signed-off-by: Stafford Horne
---
I think a patch like this will help restore the behavior.
On Sun, Feb 28, 2016 at 12:18 AM, Stafford Horne wrote:
>
>
> On Thu, 25 Feb 2016, David Miller wrote:
>
>> From: Amitoj Kaur Chawla
>> Date: Wed, 24 Feb 2016 19:28:19 +0530
>>
>>> Convert a call to init_timer and accompanying intializations of
>>> the timer's data and function fields to a call t
On Sat, 2016-02-27 at 10:19 -0800, Peter Hurley wrote:
> Hi Eric,
>
> For a while now, we've been struggling to understand why we've been
> observing missed uart rx DMA.
>
> Because both the uart driver (omap8250) and the dmaengine driver
> (edma) were (relatively) new, we assumed there was some
From: Saeed Mahameed
Date: Thu, 25 Feb 2016 18:33:19 +0200
> @@ -246,11 +246,11 @@ int mlx5_alloc_map_uar(struct mlx5_core_dev *mdev,
> struct mlx5_uar *uar)
> err = -ENOMEM;
> goto err_free_uar;
> }
> -
> - if (mdev->priv.bf_mapping)
> - uar->bf
From: Peter Hurley
Date: Sat, 27 Feb 2016 18:10:27 -0800
> That tasklet should run before any process.
You never have this guarantee, even before Eric's patch.
Under load tasklets run from ksoftirqd just like any other
softirq.
Please fix your driver and stop blaming Eric's change.
Thank you.
On Fri, Feb 26, 2016 at 8:24 PM, John Fastabend
wrote:
> On 16-02-26 09:39 AM, Cong Wang wrote:
>> On Fri, Feb 26, 2016 at 7:53 AM, John Fastabend
>> wrote:
>>> diff --git a/include/net/pkt_cls.h b/include/net/pkt_cls.h
>>> index 2121df5..e64d20b 100644
>>> --- a/include/net/pkt_cls.h
>>> +++ b/i
On Sat, Feb 27, 2016 at 5:08 AM, Jamal Hadi Salim wrote:
> From: Jamal Hadi Salim
>
> Example usage:
> Set the skb priority using skbedit then allow it to be encoded
>
> sudo tc qdisc add dev $ETH root handle 1: prio
> sudo tc filter add dev $ETH parent 1: protocol ip prio 10 \
>
On Sat, Feb 27, 2016 at 5:08 AM, Jamal Hadi Salim wrote:
> From: Jamal Hadi Salim
>
> Example usage:
> Set the skb using skbedit then allow it to be encoded
>
> sudo tc qdisc add dev $ETH root handle 1: prio
> sudo tc filter add dev $ETH parent 1: protocol ip prio 10 \
> u32 match ip protocol 1 0
On Sat, Feb 27, 2016 at 5:08 AM, Jamal Hadi Salim wrote:
> From: Jamal Hadi Salim
>
> This action allows for a sending side to encapsulate arbitrary metadata
> which is decapsulated by the receiving end.
> The sender runs in encoding mode and the receiver in decode mode.
> Both sender and receive
After commit 52bd2d62ce67 ("net: better skb->sender_cpu and skb->napi_id
cohabitation")
skb_sender_cpu_clear() becomes empty and can be removed.
Cc: Eric Dumazet
Signed-off-by: Cong Wang
---
include/linux/skbuff.h | 4
net/bridge/br_forward.c | 1 -
net/core/filter.c
Now in sctp_remaddr_seq_show(), we use variable *tsp to get the param *v.
but *tsp is also used to traversal transport_addr_list, which will cover
the previous value, and make sctp_transport_put work on the wrong transport.
So fix it by adding a new variable to get the param *v.
Fixes: fba4c330c5
v2:
Dropped module parameter from [PATCH 11/13] as suggested by David Miller
Series is generated against net-next but also applies against Linus's tip
cleanly. Entire patchset is available at below git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git
for_4.6/net-next/rds_
RDS iWarp support code has become stale and non testable. As
indicated earlier, am dropping the support for it.
If new iWarp user(s) shows up in future, we can adapat the RDS IB
transprt for the special RDMA READ sink case. iWarp needs an MR
for the RDMA READ sink.
Signed-off-by: Santosh Shilimka
The SO_TIMESTAMP generates time stamp for each incoming RDS messages
User app can enable it by using SO_TIMESTAMP setsocketopt() at
SOL_SOCKET level. CMSG data of cmsg type SO_TIMESTAMP contains the
time stamp in struct timeval format.
Reviewed-by: Sowmini Varadhan
Signed-off-by: Santosh Shilimka
Keep fmr related filed in its own struct. Fastreg MR structure
will be added to the union.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/ib_fmr.c | 17 ++---
net/rds/ib_mr.h | 11 +--
net/rds/ib_rdma.c | 14 ++
3 files changed,
Acked-by: Chien Yen
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
MAINTAINERS | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 27393cf..08b084a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9067,10 +9067,14 @@ S:
No functional changes. This is in preperation towards adding
fastreg memory resgitration support.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/Makefile | 2 +-
net/rds/ib.c | 37 +++---
net/rds/ib.h | 25 +---
net/rds/ib_fmr.c | 217 +
This helps to combine asynchronous fastreg MR completion handler
with send completion handler.
No functional change.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/ib.h | 1 -
net/rds/ib_cm.c | 42 +++---
net/rds/ib_sen
Drop the RDS connection on RDMA_CM_EVENT_TIMEWAIT_EXIT so that
it can reconnect and resume.
While testing fastreg, this error happened in couple of tests but
was getting un-noticed.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/rdma_transport.c | 8
1 f
Preperatory patch for FRMR support. From connection info,
we can retrieve cm_id which contains qp handled needed for
work request posting.
We also need to drop the RDS connection on QP error states
where connection handle becomes useful.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Sh
No functional change.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/ib_fmr.c | 126 +-
net/rds/ib_mr.h | 6 +++
net/rds/ib_rdma.c | 108 ++
3 files changed, 134 i
Add MR reuse statistics to RDS IB transport.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/ib.h | 2 ++
net/rds/ib_rdma.c | 7 ++-
net/rds/ib_stats.c | 2 ++
3 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/net/rds/ib.h b/net/rds/ib.h
ind
From: Avinash Repaka
Fastreg MR(FRMR) is another method with which one can
register memory to HCA. Some of the newer HCAs supports only fastreg
mr mode, so we need to add support for it to have RDS functional
on them.
Signed-off-by: Santosh Shilimkar
Signed-off-by: Avinash Repaka
Signed-off-by
Discovere Fast Memmory Registration support using IB device
IB_DEVICE_MEM_MGT_EXTENSIONS. Certain HCA might support just FRMR
or FMR or both FMR and FRWR. In case both mr type are supported,
default FMR is used.
Default MR is still kept as FMR against what everyone else
is following. Default will
Fastreg MR(FRMR) memory registration and invalidation makes use
of work request and completion queues for its operation. Patch
allocates extra queue space towards these operation(s).
Signed-off-by: Santosh Shilimkar
Signed-off-by: Santosh Shilimkar
---
net/rds/ib.h| 4
net/rds/ib_cm.c
On sam., 2016-02-27 at 18:10 -0800, Peter Hurley wrote:
> On 02/27/2016 05:59 PM, Eric Dumazet wrote:
> > On sam., 2016-02-27 at 15:33 -0800, Peter Hurley wrote:
> >> On 02/27/2016 03:04 PM, David Miller wrote:
> >>> From: Peter Hurley
> >>> Date: Sat, 27 Feb 2016 12:29:39 -0800
> >>>
> Not r
Hi Dave,
On 2/26/16 9:43 PM, Santosh Shilimkar wrote:
Series is generated against net-next but also applies against Linus's tip
cleanly. The diff-stat looks bit scary since almost ~4K lines of code is
getting removed.
[...]
Entire patchset is available below git tree:
git://git.ker
On 02/27/2016 05:59 PM, Eric Dumazet wrote:
> On sam., 2016-02-27 at 15:33 -0800, Peter Hurley wrote:
>> On 02/27/2016 03:04 PM, David Miller wrote:
>>> From: Peter Hurley
>>> Date: Sat, 27 Feb 2016 12:29:39 -0800
>>>
Not really. softirq raised from interrupt context will always execute
As the member .cmp_addr of sctp_af_inet6, sctp_v6_cmp_addr should also check
the port of addresses, just like sctp_v4_cmp_addr, cause it's invoked by
sctp_cmp_addr_exact().
Now sctp_v6_cmp_addr just check the port when two addresses have different
family, and lack the port check for two ipv6 addre
On sam., 2016-02-27 at 15:33 -0800, Peter Hurley wrote:
> On 02/27/2016 03:04 PM, David Miller wrote:
> > From: Peter Hurley
> > Date: Sat, 27 Feb 2016 12:29:39 -0800
> >
> >> Not really. softirq raised from interrupt context will always execute
> >> on this cpu and not in ksoftirqd, unless load
КЛИЕНТСКИЕ БАЗЫ!
Соберем для Вас по интернет базу данных потенциальных клиентов
для Вашего Бизнеса!
Много! Быстро! Недорого!
Узнайте об этом подробнее по
Тел: +79133913837
Viber: +79133913837
Whatsapp: +79133913837
Skype: prodawez389
Email: mloginov...@gmail.com
--
We are donating to you 1,500,000 GBP, from David and Carol Martin £33million
lottery, contact : davidcar...@yahoo.com.hk
view link:
http://www.ibtimes.co.uk/lotto-winners-david-carol-martin-want-blast-into-space-after-buying-new-shoes-1537851
On 02/27/2016 03:04 PM, David Miller wrote:
> From: Peter Hurley
> Date: Sat, 27 Feb 2016 12:29:39 -0800
>
>> Not really. softirq raised from interrupt context will always execute
>> on this cpu and not in ksoftirqd, unless load forces softirq loop abort.
>
> That guarantee never was specified.
From: Peter Hurley
Date: Sat, 27 Feb 2016 12:29:39 -0800
> Not really. softirq raised from interrupt context will always execute
> on this cpu and not in ksoftirqd, unless load forces softirq loop abort.
That guarantee never was specified.
Or are you saying that by design, on a system under loa
On Fri, Feb 26, 2016 at 12:46 PM, David Miller wrote:
> From: Willem de Bruijn
> Date: Fri, 26 Feb 2016 12:33:13 -0500
>
>> Right. The simplest, if hacky, fix is to add something along the lines of
>>
>> static unsigned short netdev_min_hard_header_len(struct net_device *dev)
>> {
>> if
From: Dan Carpenter
Date: Sat, 27 Feb 2016 14:31:43 +0300
> We intended to return PTR_ERR() here instead of 1.
>
> Fixes: 1f9993f6825f ('rocker: fix a neigh entry leak issue')
> Signed-off-by: Dan Carpenter
Applied, thanks.
On Sat, Feb 27, 2016 at 12:54 PM, Tom Herbert wrote:
> On Sat, Feb 27, 2016 at 11:31 AM, Jiri Benc wrote:
>> On Fri, 26 Feb 2016 15:51:29 -0800, Tom Herbert wrote:
>>> I don't think this is right. VXLAN-GPE is a separate protocol than
>>> VXLAN, they are not compatible on the wire and don't share
On Sat, Feb 27, 2016 at 11:31 AM, Jiri Benc wrote:
> On Fri, 26 Feb 2016 15:51:29 -0800, Tom Herbert wrote:
>> I don't think this is right. VXLAN-GPE is a separate protocol than
>> VXLAN, they are not compatible on the wire and don't share flags or
>> fields (for instance GPB uses bits in VXLAN th
On 02/27/2016 12:13 PM, Eric Dumazet wrote:
> On sam., 2016-02-27 at 10:19 -0800, Peter Hurley wrote:
>> Hi Eric,
>>
>> For a while now, we've been struggling to understand why we've been
>> observing missed uart rx DMA.
>>
>> Because both the uart driver (omap8250) and the dmaengine driver
>> (edm
On sam., 2016-02-27 at 10:19 -0800, Peter Hurley wrote:
> Hi Eric,
>
> For a while now, we've been struggling to understand why we've been
> observing missed uart rx DMA.
>
> Because both the uart driver (omap8250) and the dmaengine driver
> (edma) were (relatively) new, we assumed there was some
On 11/02/16 14:38, Ezequiel Garcia wrote:
(let's expand the Cc a bit)
On 10 February 2016 at 19:57, Andrew Lunn wrote:
On Wed, Feb 10, 2016 at 07:40:54PM +0100, Thomas Schlöter wrote:
Am 08.02.2016 um 19:49 schrieb Thomas Schlöter :
Am 07.02.2016 um 22:07 schrieb Thomas Schlöter :
Am 07
The current reserved_tailroom calculation fails to take hlen and tlen into
account.
skb:
[__hlen__|__data|__tlen___|__extra__]
^ ^
headskb_end_offset
In this representation, hlen + data + tlen is
On Sat, 27 Feb 2016 20:21:59 +0100, Jiri Benc wrote:
> You mean returning ETH_P_TEB in skb->protocol? That's not much useful,
> unfortunately. You won't get such packet processed by the kernel IP
> stack, rendering the VXLAN-GPE device unusable outside of ovs. It would
> effectively became a packet
On Fri, 26 Feb 2016 15:51:29 -0800, Tom Herbert wrote:
> I don't think this is right. VXLAN-GPE is a separate protocol than
> VXLAN, they are not compatible on the wire and don't share flags or
> fields (for instance GPB uses bits in VXLAN that hold the next
> protocol in VXLAN-GPE). Neither is the
On Fri, 26 Feb 2016 15:42:29 -0800, Tom Herbert wrote:
> Agreed, and I don't see why there even needs to be modes. VXLAN-GPE
> can carry arbitrary protocols with a next-header field. For Ethernet,
> MPLS, IPv4, and IPv6 it should just be a simple mapping of the next
> header to Ethertype for purpos
On Fri, 26 Feb 2016 14:22:03 -0800, Jesse Gross wrote:
> Given that VXLAN_GPE_MODE_L3 will eventually come to be used by NSH,
> MPLS, etc. in addition to IPv4/v6, most of which are not really L3, it
> seems like something along the lines of NO_ARP might be better since
> that's what it really indic
On Thu, 25 Feb 2016, David Miller wrote:
From: Amitoj Kaur Chawla
Date: Wed, 24 Feb 2016 19:28:19 +0530
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
The Coccinelle semantic patch that fixes this problem is
as
> Instead of taking the device out of suspended mode to perform the required
> action, the driver is moving to a model where 1) said action may be
> scheduled to a later time - or result from past time work - and 2) rpm handler
> must handle a lot of pm unrelated work.
>
> rtl8169_ethtool_ops.{ge
Hi Eric,
For a while now, we've been struggling to understand why we've been
observing missed uart rx DMA.
Because both the uart driver (omap8250) and the dmaengine driver
(edma) were (relatively) new, we assumed there was some race between
starting a new rx DMA and processing the previous one.
Commit f1705ec197e70 allows IPv6 addresses to be retained on a link down.
The address can have a cached host route which can point to the wrong
FIB table if the L3 enslavement is changed (e.g., route can point to local
table instead of VRF table if device is added to an L3 domain).
On link up chec
Use managed resource functions devm_kzalloc and pcim_enable_device
to simplify error handling. Subsequently, remove unnecessary
kfree, pci_disable_device and pci_release_regions.
To be compatible with the change, various gotos are replaced with
direct returns and unneeded labels are dropped.
Also
Hi,
Couple of checkpatch complains:
Christoph Hellwig wrote on Sat, Feb 27, 2016:
> -struct p9_rdma_context {
> - enum ib_wc_opcode wc_op;
> +struct p9_rdma_context {
trailing tab
> - p9_debug(P9_DEBUG_ERROR, "req %p err %d status %d\n", req, err, status);
> + p9_debug(P9_DEBUG
From: Jamal Hadi Salim
As agreed at netconf in Seville, here's the patch finally (1 year
was just too long to wait for an ethertype. Now we are just going
have the user configure one).
Described in netdev01 paper:
"Distributing Linux Traffic Control Classifier-Action Subsystem"
From: Jamal Hadi Salim
Example usage:
Set the skb using skbedit then allow it to be encoded
sudo tc qdisc add dev $ETH root handle 1: prio
sudo tc filter add dev $ETH parent 1: protocol ip prio 10 \
u32 match ip protocol 1 0xff flowid 1:2 \
action skbedit mark 17 \
action ife encode \
allow mark
From: Jamal Hadi Salim
Example usage:
Set the skb priority using skbedit then allow it to be encoded
sudo tc qdisc add dev $ETH root handle 1: prio
sudo tc filter add dev $ETH parent 1: protocol ip prio 10 \
u32 match ip protocol 1 0xff flowid 1:2 \
action skbedit prio 17
From: Jamal Hadi Salim
This action allows for a sending side to encapsulate arbitrary metadata
which is decapsulated by the receiving end.
The sender runs in encoding mode and the receiver in decode mode.
Both sender and receiver must specify the same ethertype.
At some point we hope to have a re
On 16-02-26 06:49 PM, Cong Wang wrote:
On Fri, Feb 26, 2016 at 2:43 PM, Jamal Hadi Salim wrote:
[...]
Just some quick reviews... ;)
;->
Ok, update in a little while after some basic testing...
cheers,
jamal
Sat, Feb 27, 2016 at 12:31:43PM CET, dan.carpen...@oracle.com wrote:
>We intended to return PTR_ERR() here instead of 1.
>
>Fixes: 1f9993f6825f ('rocker: fix a neigh entry leak issue')
>Signed-off-by: Dan Carpenter
Acked-by: Jiri Pirko
We intended to return PTR_ERR() here instead of 1.
Fixes: 1f9993f6825f ('rocker: fix a neigh entry leak issue')
Signed-off-by: Dan Carpenter
---
We recently moved rocker files around so this only applies to -next.
Probably returning the wrong error code is harmless.
diff --git a/drivers/net/ethe
Hi all,
who is maintaining the "RDMA transport" (1) for 9p? Below patch converts
it to your new CQ API. It's fairly trivial, but untested as I can't figure
out how to actually test this code.
[1] RDMA seems a bit of a misowner as it's never doing RDMA data transfers,
but that's a separate story
Trivial conversion to the new RDMA CQ API.
Signed-off-by: Christoph Hellwig
---
net/9p/trans_rdma.c | 87 +++--
1 file changed, 31 insertions(+), 56 deletions(-)
diff --git a/net/9p/trans_rdma.c b/net/9p/trans_rdma.c
index 52b4a2f..668c3be 100644
TCP probe log timestamps use struct timespec which is
not y2038 safe. Even though timespec might be good enough here
as it is used to represent delta time, the plan is to get rid
of all uses of timespec in the kernel.
Replace with struct timespec64 which is y2038 safe.
Prints still use unsigned lo
SCTP probe log timestamps use struct timespec which is
not y2038 safe.
Use struct timespec64 which is 2038 safe instead.
Use monotonic time instead of real time as only time
differences are logged.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Acked-by: Neil Horman
Cc: Vlad Yasevich
ICMP timestamp messages and IP source route options require
timestamps to be in milliseconds modulo 24 hours from
midnight UT format.
Add inet_current_timestamp() function to support this. The function
returns the required timestamp in network byte order.
Timestamp calculation is also changed to
Introduction:
The series is aimed at transitioning network timestamps to being
y2038 safe.
All patches can be reviewed and merged independently.
Socket timestamps and ioctl calls will be handled separately.
Thanks to Arnd Bergmann for discussing solution options with me.
Solution:
Data type st
> +{
> + asm("lea 40f(, %[slen], 4), %%r11\n\t"
> + "clc\n\t"
> + "jmpq *%%r11\n\t"
> + "adcq 7*8(%[src]),%[res]\n\t"
> + "adcq 6*8(%[src]),%[res]\n\t"
> + "adcq 5*8(%[src]),%[res]\n\t"
> + "adcq 4*8(%[src]),%[res]\n\t"
> +
67 matches
Mail list logo
