[no subject]

внимания; Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных администратором, который в настоящее время работает на 10.9GB, Вы не сможете отправить или получить новую почту, пока вы повторно не проверить ваш почтовый ящик почты. Чтобы восстановить работоспособность

Re: [PATCH for-next V2 00/11] Mellanox mlx5 core and ODP updates 2017-01-01

On Tue, Jan 03, 2017 at 01:30:16AM +0200, Saeed Mahameed wrote: > On Mon, Jan 2, 2017 at 10:53 PM, David Miller wrote: > > From: Saeed Mahameed > > Date: Mon, 2 Jan 2017 11:37:37 +0200 > > > >> The following eleven patches mainly come from Artemy

Re: [PATCH net 9/9] virtio-net: XDP support for small buffers

On 2017年01月03日 06:43, John Fastabend wrote: On 16-12-23 06:37 AM, Jason Wang wrote: Commit f600b6905015 ("virtio_net: Add XDP support") leaves the case of small receive buffer untouched. This will confuse the user who want to set XDP but use small buffers. Other than forbid XDP in small

Re: [net PATCH] net: virtio: cap mtu when XDP programs are running

On 2017年01月03日 06:30, John Fastabend wrote: XDP programs can not consume multiple pages so we cap the MTU to avoid this case. Virtio-net however only checks the MTU at XDP program load and does not block MTU changes after the program has loaded. This patch sets/clears the max_mtu value at XDP

Re: [RFC PATCH] virtio_net: XDP support for adjust_head

On 2017年01月03日 03:44, John Fastabend wrote: Add support for XDP adjust head by allocating a 256B header region that XDP programs can grow into. This is only enabled when a XDP program is loaded. In order to ensure that we do not have to unwind queue headroom push queue setup below

[PATCHv2 net-next 3/3] sctp: remove asoc ssnmap and ssnmap.c

Since asoc stream arrays has replaced ssnmap, ssnmap is not used any more, this patch is to remove asoc ssnmap and ssnmap.c. Signed-off-by: Xin Long --- include/net/sctp/sctp.h| 1 - include/net/sctp/structs.h | 33 net/sctp/Makefile | 3 +-

[PATCHv2 net-next 1/3] sctp: add stream arrays in asoc

This patch is to add streamout and streamin arrays in asoc, initialize them in sctp_process_init and free them in sctp_association_free. Stream arrays are used to replace ssnmap to save more stream things in the next patch. Signed-off-by: Xin Long ---

[PATCHv2 net-next 2/3] sctp: replace ssnmap with asoc stream arrays

Stream arrays are used to save per stream information, which includes ssn for each stream already. This patch is to replace ssnmap with asoc stream arrays. Signed-off-by: Xin Long --- include/net/sctp/structs.h | 19 ++- net/sctp/associola.c | 10

[PATCHv2 net-next 0/3] sctp: prepare asoc stream for stream reconf

sctp stream reconf, described in RFC 6525, needs a structure to save per stream information in assoc, like stream state. In the future, sctp stream scheduler also needs it to save some stream scheduler params and queues. This patchset is to prepare the stream array in assoc for stream reconf.

Re: [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM.

Hi Richard, On Mon, Jan 2, 2017 at 9:43 PM, Richard Cochran wrote: > On Mon, Jan 02, 2017 at 03:47:07PM +0100, Nicolas Ferre wrote: >> Le 02/01/2017 à 12:31, Richard Cochran a écrit : >> > This Cadence IP core is a complete disaster. >> >> Well, it evolved and propose

Re: [PATCH net-next] net/sched: cls_flower: Add user specified data

On 17-01-02 05:22 PM, Jamal Hadi Salim wrote: > On 17-01-02 05:58 PM, John Fastabend wrote: >> On 17-01-02 02:21 PM, Jamal Hadi Salim wrote: > > >> Well having the length value avoids ending up with cookie1, cookie2, ... >> values as folks push more and more data into the cookie. >> > > Unless

Re: [PATCH net-next V3 3/3] tun: rx batching

On 2017年01月01日 05:03, Stephen Hemminger wrote: On Fri, 30 Dec 2016 13:20:51 +0800 Jason Wang wrote: diff --git a/drivers/net/tun.c b/drivers/net/tun.c index cd8e02c..a268ed9 100644 --- a/drivers/net/tun.c +++ b/drivers/net/tun.c @@ -75,6 +75,10 @@ #include

Re: [PATCH net-next V3 3/3] tun: rx batching

On 2017年01月01日 01:31, David Miller wrote: From: Jason Wang Date: Fri, 30 Dec 2016 13:20:51 +0800 @@ -1283,10 +1314,15 @@ static ssize_t tun_get_user(struct tun_struct *tun, struct tun_file *tfile, skb_probe_transport_header(skb, 0); rxhash =

linux-next: manual merge of the rdma-leon tree with the net-next tree

Hi Leon, Today's linux-next merge of the rdma-leon tree got conflicts in: drivers/infiniband/hw/mlx5/main.c drivers/infiniband/hw/mlx5/mlx5_ib.h drivers/infiniband/hw/mlx5/mr.c drivers/infiniband/hw/mlx5/qp.c drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c

Re: [PATCH net-next] net/sched: cls_flower: Add user specified data

On 17-01-02 05:58 PM, John Fastabend wrote: On 17-01-02 02:21 PM, Jamal Hadi Salim wrote: Well having the length value avoids ending up with cookie1, cookie2, ... values as folks push more and more data into the cookie. Unless there is good reason I dont see why it shouldnt be a fixed

RE: [PATCH v2] scm: fix possible control message header alignment issue

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Saturday, December 31, 2016 4:21 AM > To: cug...@163.com > Cc: netdev@vger.kernel.org; YUAN Linyu > Subject: Re: [PATCH v2] scm: fix possible control message header alignment > issue > If you can come up with

Re: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable

On Sat, Dec 31, 2016 at 4:07 PM, Ansis Atteka wrote: > On Wed, Nov 30, 2016 at 3:58 AM, Hayes Wang wrote: >> Mark Lord >> [...] >>> > Not sure why, because there really is no other way for the data to >>> > appear where it does at the

[PATCH] drop_monitor: consider inserted data in genlmsg_end

Final nlmsg_len field update must reflect inserted net_dm_drop_point data. This patch depends on previous patch: "drop_monitor: add missing call to genlmsg_end" Signed-off-by: Reiter Wolfgang --- net/core/drop_monitor.c | 8 +++- 1 file changed, 7 insertions(+), 1

Re: [PATCH] drop_monitor: consider inserted data in genlmsg_end

From: Reiter Wolfgang Date: Tue, 3 Jan 2017 00:34:10 +0100 > Final nlmsg_len field update must reflect inserted net_dm_drop_point > data. > > This patch depends on previous patch: > "drop_monitor: add missing call to genlmsg_end" > > Signed-off-by: Reiter Wolfgang

Re: [PATCH v2 2/2] net: sfc: falcon: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 19:02:46 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes > --- > Changelog: > v2: > - simplify the code of

Re: [PATCH] net: dlink: dl2k: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 20:49:26 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > The previous implementation of set_settings was modifying > the value of speed and duplex, but with

Re: [PATCH v2 1/2] net: mdio: add mdio45_ethtool_ksettings_get

From: Philippe Reynes Date: Sun, 1 Jan 2017 19:02:45 +0100 > There is a function in mdio for the old ethtool api gset. > We add a new function mdio45_ethtool_ksettings_get for the > new ethtool api glinksettings. > > Signed-off-by: Philippe Reynes > --- >

Re: [PATCH] net: dlink: sundance: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 20:52:12 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: dec: de2104x: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 19:05:38 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: emulex: benet: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Mon, 2 Jan 2017 17:42:14 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: dec: uli526x: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 19:11:06 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: faraday: ftmac100: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Mon, 2 Jan 2017 19:53:11 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: fealnx: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Mon, 2 Jan 2017 20:47:27 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] net: dec: winbond-840: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 1 Jan 2017 20:47:01 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Applied.

[PATCH] drop_monitor: consider inserted data in genlmsg_end

Final nlmsg_len field update must reflect inserted net_dm_drop_point data. This patch depends on previous patch: "drop_monitor: add missing call to genlmsg_end" Signed-off-by: Reiter Wolfgang --- net/core/drop_monitor.c | 7 ++- 1 file changed, 6 insertions(+), 1

Re: [PATCH for-next V2 00/11] Mellanox mlx5 core and ODP updates 2017-01-01

On Mon, Jan 2, 2017 at 10:53 PM, David Miller wrote: > From: Saeed Mahameed > Date: Mon, 2 Jan 2017 11:37:37 +0200 > >> The following eleven patches mainly come from Artemy Kovalyov >> who expanded mlx5 on-demand-paging (ODP) support. In addition >>

Re: [PATCH v2 net-next 2/2] tools: test case for TPACKET_V3/TX_RING support

On Mon, Jan 2, 2017 at 6:02 PM, Sowmini Varadhan wrote: > On (01/02/17 17:31), Willem de Bruijn wrote: >> >> Thanks for adding this. >> >> walk_v3_tx is almost identical to walk_v1_v2_tx. That function can >> just be extended to add a v3 case where it already

Re: tcp_bbr: Forcing set of BBR congestion control as default

On Mon, Jan 2, 2017 at 2:30 PM, Sedat Dilek wrote: > OK, this looks now good. Great. Glad to hear it! > Does BBR only work with fq-qdisc best? Yes. BBR is designed to work with pacing. And so far the "fq" qdisc is the only qdisc that offers pacing. So BBR currently needs

Re: [PATCH v2 net-next 1/2] af_packet: TX_RING support for TPACKET_V3

On (01/02/17 17:57), Willem de Bruijn wrote: > One more point. We should validate the tpacket_req3 input and fail if > unsupported options are passed. Specifically, fail if any of > {tp_retire_blk_tov, tp_sizeof_priv, tp_feature_req_word} is non-zero. > > Otherwise looks good to me. Ok, I'll

Re: [PATCH v2 net-next 2/2] tools: test case for TPACKET_V3/TX_RING support

On (01/02/17 17:31), Willem de Bruijn wrote: > > Thanks for adding this. > > walk_v3_tx is almost identical to walk_v1_v2_tx. That function can > just be extended to add a v3 case where it already multiplexes between > v1 and v2. I looked at that, but the sticky point is that v1/v2 sets up the

Re: [PATCH net-next] net/sched: cls_flower: Add user specified data

On 17-01-02 02:21 PM, Jamal Hadi Salim wrote: > On 17-01-02 01:23 PM, John Fastabend wrote: > >> >> Additionally I would like to point out this is an arbitrary length binary >> blob (for undefined use, without even a specified encoding) that gets pushed >> between user space and hardware ;) This

Re: [PATCH v2 net-next 1/2] af_packet: TX_RING support for TPACKET_V3

On Sun, Jan 1, 2017 at 5:45 PM, Sowmini Varadhan wrote: > Although TPACKET_V3 Rx has some benefits over TPACKET_V2 Rx, *_v3 > does not currently have TX_RING support. As a result an application > that wants the best perf for Tx and Rx (e.g. to handle request/response

[net-next][PATCH v3 00/17] net: RDS updates

v2->v3: - Re-based against latest net-next head. - Dropped a user visible change after discussing with David Miller. It needs some more work to fully support old/new tools matrix. - Addressed Dave's comment about bool usage in patch "RDS: IB: track and log active side..." v1->v2: Re-aligned

[net-next][PATCH v3 04/17] RDS: IB: make the transport retry count smallest

Transport retry is not much useful since it indicate packet loss in fabric so its better to failover fast rather than longer retry. Signed-off-by: Santosh Shilimkar --- net/rds/ib.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/rds/ib.h

[net-next][PATCH v3 08/17] RDS: IB: split the mr registration and invalidation path

MR invalidation in RDS is done in background thread and not in data path like registration. So break the dependency between them which helps to remove the performance bottleneck. Signed-off-by: Santosh Shilimkar --- net/rds/ib.h | 4 +++- net/rds/ib_cm.c |

[net-next][PATCH v3 05/17] RDS: RDMA: fix the ib_map_mr_sg_zbva() argument

Fixes warning: Using plain integer as NULL pointer Signed-off-by: Santosh Shilimkar --- net/rds/ib_frmr.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/net/rds/ib_frmr.c b/net/rds/ib_frmr.c index d921adc..66b3d62 100644 ---

[net-next][PATCH v3 09/17] RDS: RDMA: silence the use_once mr log flood

In absence of extension headers, message log will keep flooding the console. As such even without use_once we can clean up the MRs so its not really an error case message so make it debug message Signed-off-by: Santosh Shilimkar --- net/rds/rdma.c | 3 ++- 1 file

[net-next][PATCH v3 02/17] RDS: mark few internal functions static to make sparse build happy

Fixes below warnings: warning: symbol 'rds_send_probe' was not declared. Should it be static? warning: symbol 'rds_send_ping' was not declared. Should it be static? warning: symbol 'rds_tcp_accept_one_path' was not declared. Should it be static? warning: symbol 'rds_walk_conn_path_info' was not

[PATCH] net: freescale: dpaa: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c | 18 +- 1 files changed, 9 insertions(+), 9 deletions(-) diff

[net-next][PATCH v3 06/17] RDS: RDMA: start rdma listening after init

From: Qing Huang This prevents RDS from handling incoming rdma packets before RDS completes initializing its recv/send components. Signed-off-by: Qing Huang Signed-off-by: Santosh Shilimkar ---

[net-next][PATCH v3 01/17] RDS: log the address on bind failure

It's useful to know the IP address when RDS fails to bind a connection. Thus, adding it to the error message. Orabug: 21894138 Reviewed-by: Wei Lin Guay Signed-off-by: Santosh Shilimkar --- net/rds/bind.c | 4 ++-- 1 file changed, 2

[net-next][PATCH v3 03/17] RDS: IB: include faddr in connection log

Also use pr_* for it. Signed-off-by: Santosh Shilimkar --- net/rds/ib_cm.c | 19 +-- net/rds/ib_recv.c | 4 ++-- net/rds/ib_send.c | 4 ++-- 3 files changed, 13 insertions(+), 14 deletions(-) diff --git a/net/rds/ib_cm.c b/net/rds/ib_cm.c index

[net-next][PATCH v3 07/17] RDS: RDMA: return appropriate error on rdma map failures

The first message to a remote node should prompt a new connection even if it is RDMA operation. For RDMA operation the MR mapping can fail because connections is not yet up. Since the connection establishment is asynchronous, we make sure the map failure because of unavailable connection reach to

[net-next][PATCH v3 15/17] RDS: add stat for socket recv memory usage

From: Venkat Venkatsubra Tracks the receive side memory added to scokets and removed from sockets. Signed-off-by: Venkat Venkatsubra Signed-off-by: Santosh Shilimkar --- net/rds/rds.h | 3 +++

[net-next][PATCH v3 11/17] RDS: IB: add few useful cache stasts

Tracks the ib receive cache total, incoming and frag allocations. Signed-off-by: Santosh Shilimkar --- net/rds/ib.h | 7 +++ net/rds/ib_recv.c | 6 ++ net/rds/ib_stats.c | 2 ++ 3 files changed, 15 insertions(+) diff --git a/net/rds/ib.h

[net-next][PATCH v3 17/17] RDS: add receive message trace used by application

Socket option to tap receive path latency in various stages in nano seconds. It can be enabled on selective sockets using using SO_RDS_MSG_RXPATH_LATENCY socket option. RDS will return the data to application with RDS_CMSG_RXPATH_LATENCY in defined format. Scope is left to add more trace points

[net-next][PATCH v3 16/17] RDS: make message size limit compliant with spec

From: Avinash Repaka RDS support max message size as 1M but the code doesn't check this in all cases. Patch fixes it for RDMA & non-RDMA and RDS MR size and its enforced irrespective of underlying transport. Signed-off-by: Avinash Repaka

[net-next][PATCH v3 13/17] RDS: RDMA: Fix the composite message user notification

When application sends an RDS RDMA composite message consist of RDMA transfer to be followed up by non RDMA payload, it expect to be notified *only* when the full message gets delivered. RDS RDMA notification doesn't behave this way though. Thanks to Venkat for debug and root casuing the issue

[net-next][PATCH v3 10/17] RDS: IB: track and log active side endpoint in connection

Useful to know the active and passive end points in a RDS IB connection. Signed-off-by: Santosh Shilimkar --- net/rds/ib.h| 3 +++ net/rds/ib_cm.c | 11 +++ 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/net/rds/ib.h b/net/rds/ib.h

[net-next][PATCH v3 14/17] RDS: IB: fix panic due to handlers running post teardown

Shutdown code reaping loop takes care of emptying the CQ's before they being destroyed. And once tasklets are killed, the hanlders are not expected to run. But because of core tasklet code issues, tasklet handler could still run even after tasklet_kill, RDS IB shutdown code already reaps the CQs

[net-next][PATCH v3 12/17] RDS: IB: Add vector spreading for cqs

Based on available device vectors, allocate cqs accordingly to get better spread of completion vectors which helps performace great deal.. Signed-off-by: Santosh Shilimkar --- net/rds/ib.c| 11 +++ net/rds/ib.h| 5 + net/rds/ib_cm.c | 40

Re: [PATCH net 9/9] virtio-net: XDP support for small buffers

On 16-12-23 06:37 AM, Jason Wang wrote: > Commit f600b6905015 ("virtio_net: Add XDP support") leaves the case of > small receive buffer untouched. This will confuse the user who want to > set XDP but use small buffers. Other than forbid XDP in small buffer > mode, let's make it work. XDP then can

[net PATCH] net: virtio: cap mtu when XDP programs are running

XDP programs can not consume multiple pages so we cap the MTU to avoid this case. Virtio-net however only checks the MTU at XDP program load and does not block MTU changes after the program has loaded. This patch sets/clears the max_mtu value at XDP load/unload time. Signed-off-by: John

Re: [PATCH v2 net-next 2/2] tools: test case for TPACKET_V3/TX_RING support

On Sun, Jan 1, 2017 at 5:45 PM, Sowmini Varadhan wrote: > Add a test case and sample code for (TPACKET_V3, PACKET_TX_RING) Thanks for adding this. walk_v3_tx is almost identical to walk_v1_v2_tx. That function can just be extended to add a v3 case where it already

[PATCH nf-next 7/7] xtables: extend matches and targets with .usersize

From: Willem de Bruijn In matches and targets that define a kernel-only tail to their xt_match and xt_target data structs, add a field .usersize that specifies up to where data is to be shared with userspace. Performed a search for comment "Used internally by the kernel" to

[PATCH nf-next 6/7] xtables: use match, target and data copy_to_user helpers in compat

From: Willem de Bruijn Convert compat to copying entries, matches and targets one by one, using the xt_match_to_user and xt_target_to_user helper functions. Signed-off-by: Willem de Bruijn --- net/netfilter/x_tables.c | 14 -- 1 file

[PATCH nf-next 4/7] arptables: use match, target and data copy_to_user helpers

From: Willem de Bruijn Convert arptables to copying entries, matches and targets one by one, using the xt_match_to_user and xt_target_to_user helper functions. Signed-off-by: Willem de Bruijn --- net/ipv4/netfilter/arp_tables.c | 15 +-- 1

[PATCH nf-next 3/7] ip6tables: use match, target and data copy_to_user helpers

From: Willem de Bruijn Convert ip6tables to copying entries, matches and targets one by one, using the xt_match_to_user and xt_target_to_user helper functions. Signed-off-by: Willem de Bruijn --- net/ipv6/netfilter/ip6_tables.c | 21

[PATCH nf-next 5/7] ebtables: use match, target and data copy_to_user helpers

From: Willem de Bruijn Convert ebtables to copying entries, matches and targets one by one. The solution is analogous to that of generic xt_(match|target)_to_user helpers, but is applied to different structs. Convert existing helpers ebt_make_XXXname helpers that overwrite

[PATCH nf-next 2/7] iptables: use match, target and data copy_to_user helpers

From: Willem de Bruijn Convert iptables to copying entries, matches and targets one by one, using the xt_match_to_user and xt_target_to_user helper functions. Signed-off-by: Willem de Bruijn --- net/ipv4/netfilter/ip_tables.c | 21 ++---

[PATCH nf-next 1/7] xtables: add xt_match, xt_target and data copy_to_user functions

From: Willem de Bruijn xt_entry_target, xt_entry_match and their private data may contain kernel data. Introduce helper functions xt_match_to_user, xt_target_to_user and xt_data_to_user that copy only the expected fields. These replace existing logic that calls copy_to_user

Re: [PATCH net-next] net/sched: cls_flower: Add user specified data

On 17-01-02 01:23 PM, John Fastabend wrote: Additionally I would like to point out this is an arbitrary length binary blob (for undefined use, without even a specified encoding) that gets pushed between user space and hardware ;) This seemed to get folks fairly excited in the past. The

[PATCH nf-next 0/7] xtables: use dedicated copy_to_user helpers

From: Willem de Bruijn xtables list and save interfaces share xt_match and xt_target state with userspace. The kernel and userspace definitions of these structs differ. Currently, the structs are copied wholesale, then patched up. The match and target structs contain a kernel

[net PATCH] ipv4: Do not allow MAIN to be alias for new LOCAL w/ custom rules

From: Alexander Duyck In the case of custom rules being present we need to handle the case of the LOCAL table being intialized after the new rule has been added. To address that I am adding a new check so that we can make certain we don't use an alias of MAIN for

Re: [PATCH for-next V2 00/11] Mellanox mlx5 core and ODP updates 2017-01-01

From: Saeed Mahameed Date: Mon, 2 Jan 2017 11:37:37 +0200 > The following eleven patches mainly come from Artemy Kovalyov > who expanded mlx5 on-demand-paging (ODP) support. In addition > there are three cleanup patches which don't change any functionality, > but are needed

Re: [PATCH net] Documentation/networking: fix typo in mpls-sysctl

From: Alexander Alemayhu Date: Mon, 2 Jan 2017 18:52:24 +0100 > s/utliziation/utilization > > Signed-off-by: Alexander Alemayhu Applied, thanks.

Re: pull-request: wireless-drivers-next 2017-01-02

From: Kalle Valo Date: Mon, 02 Jan 2017 15:20:59 +0200 > first pull request for 4.11. The tree is based on 4.9 but that shouldn't > be a problem, at least my test pull to net-next worked ok. I'll fast > forward my trees after you have pulled this. > > Please let me know if

Re: [PATCH] tcp: provide tx timestamps for partial writes

On Mon, Jan 2, 2017 at 3:20 PM, Soheil Hassas Yeganeh wrote: > From: Soheil Hassas Yeganeh > > For TCP sockets, tx timestamps are only captured when the user data > is successfully and fully written to the socket. In many cases, > however, TCP writes can

[PATCH] tcp: provide tx timestamps for partial writes

From: Soheil Hassas Yeganeh For TCP sockets, tx timestamps are only captured when the user data is successfully and fully written to the socket. In many cases, however, TCP writes can be partial for which no timestamp is collected. Collect timestamps when the user data is

Re: [PATCH 02/12] Common functions and definitions

> +#define AQ_OBJ_SET(_OBJ_, _F_) \ > +{ unsigned long flags_old, flags_new; atomic_t *flags = &(_OBJ_)->flags; \ > +do { \ > + flags_old = atomic_read(flags); \ > + flags_new = flags_old | (_F_); \ > +} while (atomic_cmpxchg(flags, \ > + flags_old, flags_new) != flags_old); } > + >

Re: [RFC PATCH] virtio_net: XDP support for adjust_head

On 17-01-02 11:44 AM, John Fastabend wrote: > Add support for XDP adjust head by allocating a 256B header region > that XDP programs can grow into. This is only enabled when a XDP > program is loaded. > > In order to ensure that we do not have to unwind queue headroom push > queue setup below

[PATCH] net: fealnx: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/fealnx.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git

[RFC PATCH] virtio_net: XDP support for adjust_head

Add support for XDP adjust head by allocating a 256B header region that XDP programs can grow into. This is only enabled when a XDP program is loaded. In order to ensure that we do not have to unwind queue headroom push queue setup below bpf_prog_add. It reads better to do a prog ref unwind vs

[PATCH net-next] bridge: multicast to unicast

Implements an optional, per bridge port flag and feature to deliver multicast packets to any host on the according port via unicast individually. This is done by copying the packet per host and changing the multicast destination MAC to a unicast one accordingly. multicast-to-unicast works on top

Re: tcp_bbr: Forcing set of BBR congestion control as default

On Mon, Jan 2, 2017 at 8:12 PM, Neal Cardwell wrote: > On Mon, Jan 2, 2017 at 1:49 PM, Sedat Dilek wrote: >> On Mon, Jan 2, 2017 at 7:17 PM, Neal Cardwell wrote: >>> On Mon, Jan 2, 2017 at 12:05 AM, Sedat Dilek

Re: tcp_bbr: Forcing set of BBR congestion control as default

On Mon, Jan 2, 2017 at 1:49 PM, Sedat Dilek wrote: > On Mon, Jan 2, 2017 at 7:17 PM, Neal Cardwell wrote: >> On Mon, Jan 2, 2017 at 12:05 AM, Sedat Dilek wrote: >>> >>> Hi, >>> >>> I am trying to force the set of BBR congestion

Re: [PATCH iproute2 net-next] tc: flower: support matching flags

On Wed, 28 Dec 2016 15:06:49 +0200, Paul Blakey wrote: > Enhance flower to support matching on flags. > > The 1st flag allows to match on whether the packet is > an IP fragment. > > Example: > > # add a flower filter that will drop fragmented packets > # (bit 0 of control flags) >

[PATCH] net: faraday: ftmac100: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/faraday/ftmac100.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git

Re: tcp_bbr: Forcing set of BBR congestion control as default

On Mon, Jan 2, 2017 at 7:17 PM, Neal Cardwell wrote: > On Mon, Jan 2, 2017 at 12:05 AM, Sedat Dilek wrote: >> >> Hi, >> >> I am trying to force the set of BBR congestion control as default. >> My old linux-config uses CUBIC as default. >> I want both

Re: [PATCH net-next] net/sched: cls_flower: Add user specified data

On 17-01-02 06:59 AM, Jamal Hadi Salim wrote: > > We have been using a cookie as well for actions (which we have been > using but have been too lazy to submit so far). I am going to port > it over to the newer kernels and post it. > In our case that is intended to be opaque to the kernel i.e

Re: tcp_bbr: Forcing set of BBR congestion control as default

On Mon, Jan 2, 2017 at 12:05 AM, Sedat Dilek wrote: > > Hi, > > I am trying to force the set of BBR congestion control as default. > My old linux-config uses CUBIC as default. > I want both BBR and CUBIC to be built but BBR shall be my default. > > I tried the below

Re: [PATCH - resubmit] igmp: Make igmp group member RFC 3376 compliant

From: Michal Tesar Date: Mon, 2 Jan 2017 14:38:36 +0100 > 5.2. Action on Reception of a Query > > When a system receives a Query, it does not respond immediately. > Instead, it delays its response by a random amount of time, bounded > by the Max Resp Time value derived

Re: [PATCH] Update pptp handling to avoid null pointer deref. v2

From: Ian Kumlien Date: Mon, 2 Jan 2017 09:18:35 +0100 > __skb_flow_dissect can be called with a skb or a data packet, either > can be NULL. All calls seems to have been moved to __skb_header_pointer > except the pptp handling which is still calling skb_header_pointer.

[PATCH net] Documentation/networking: fix typo in mpls-sysctl

s/utliziation/utilization Signed-off-by: Alexander Alemayhu --- Documentation/networking/mpls-sysctl.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/mpls-sysctl.txt b/Documentation/networking/mpls-sysctl.txt index

Re: pull-request: mac80211 2017-01-02

From: Johannes Berg Date: Mon, 2 Jan 2017 15:39:03 +0100 > Happy New Year :-) Same to you :-) > Even though I was out for around two weeks, only a single fix came in, > I guess everyone else was also out. But if people were out, then they > won't be sending fixes

[PATCH 1/1] igb: Fix hw_dbg logging in igb_update_flash_i210

From: Hannu Lounento Fix an if statement with hw_dbg lines where the logic was inverted with regards to the corresponding return value used in the if statement. Signed-off-by: Hannu Lounento Signed-off-by: Peter Senna Tschudin

Re: Bug w/ (policy) routing

On Mon, 2 Jan 2017 09:48:12 -0700 David Ahern wrote: > On 1/1/17 12:52 PM, Olivier Brunel wrote: > > Indeed, if I first delete the rule for lookup local and recreate it > > w/ higher prio than my "lookup 50", then no more issue. > > After the unshare or when creating

Re: Bug w/ (policy) routing

On 1/1/17 12:52 PM, Olivier Brunel wrote: > Indeed, if I first delete the rule for lookup local and recreate it > w/ higher prio than my "lookup 50", then no more issue. After the unshare or when creating a new network namespace, bringing the lo device up will create the local table and the rest

[PATCH] net: emulex: benet: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/emulex/benet/be_ethtool.c | 73 +++- 1 files changed, 34 insertions(+), 39 deletions(-)

Re: [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM.

On Mon, Jan 02, 2017 at 03:47:07PM +0100, Nicolas Ferre wrote: > Le 02/01/2017 à 12:31, Richard Cochran a écrit : > > This Cadence IP core is a complete disaster. > > Well, it evolved and propose several options to different SoC > integrators. This is not something unusual... > I suspect as well

Re: [PATCH net-next rfc 0/6] convert tc_verd to integer bitfields

And a happy new year netdev. No objections to new year resolution of slimming the skb. But: i am still concerned about the recursion that getting rid of some of these bits could embolden. i.e my suggestion was infact to restore some of those bits taken away by Florian after the ingress redirect

Re: [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM.

On Mon, Jan 02, 2017 at 05:13:34PM +0530, Harini Katakam wrote: > From the revision history of Cadence spec, all versions starting > r1p02 have ability to include timestamp in descriptors. So why not add code to read the version, hm? > For previous versions the event register is the only option.

Re: [PATCH net 0/3] net: stmmac: dwmac-oxnas: fix leaks and simplify pm

On 01/02/2017 12:56 PM, Johan Hovold wrote: > These patches fixes of-node and fixed-phydev leaks in the recently added > dwmac-oxnas driver, and ultimately switches over to using the generic pm > implementation as the required callbacks are now in place. > > Note that this series has only been

Re: [PATCH] rfkill: remove rfkill-regulator

On Mon, 2017-01-02 at 16:01 +0100, Johannes Berg wrote: > From: Johannes Berg > > There are no users of this ("vrfkill") in the tree, so it's just > dead code - remove it. > > This also isn't really how rfkill is supposed to be used - it's > intended as a signalling

[PATCH] rfkill: remove rfkill-regulator

From: Johannes Berg There are no users of this ("vrfkill") in the tree, so it's just dead code - remove it. This also isn't really how rfkill is supposed to be used - it's intended as a signalling mechanism to/from the device, which the driver (and partially cfg80211)

  1   2   >