Re: [PATCH v7 RESEND 0/4] mailbox: hisilicon: add Hi6220 mailbox driver

Hi Leo and Jassi, On 26/02/2016 19:40, Jassi Brar wrote: > On Mon, Feb 15, 2016 at 7:20 PM, Leo Yan wrote: >> Hi6220 mailbox supports up to 32 channels. Each channel is unidirectional >> with a maximum message size of 8 words. I/O is performed using register >> access (there

Re: [PATCH v7 RESEND 0/4] mailbox: hisilicon: add Hi6220 mailbox driver

Hi Leo and Jassi, On 26/02/2016 19:40, Jassi Brar wrote: > On Mon, Feb 15, 2016 at 7:20 PM, Leo Yan wrote: >> Hi6220 mailbox supports up to 32 channels. Each channel is unidirectional >> with a maximum message size of 8 words. I/O is performed using register >> access (there is no DMA) and the

Re: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

On Fri, 26 Feb 2016, John Stultz wrote: > clocksource: introduce clocksource_freq2mult() > jiffies: use CLOCKSOURCE_MASK instead of constant Bah. You again forgot to make the first letter of the sentence upper case. Hint: There is the concept of scripts, which can automate that :)

Re: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

On Fri, 26 Feb 2016, John Stultz wrote: > clocksource: introduce clocksource_freq2mult() > jiffies: use CLOCKSOURCE_MASK instead of constant Bah. You again forgot to make the first letter of the sentence upper case. Hint: There is the concept of scripts, which can automate that :)

Re: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

John, On Fri, 26 Feb 2016, John Stultz wrote: > Hey Thomas, Ingo, > Here's my somewhat truncated queue for 4.6. I was hoping to > get the cross-timestamp patchset from Christopher sent along, > but he's got some last minute changes to address feedback from > Andy, so I'm holding off. > > If

Re: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

John, On Fri, 26 Feb 2016, John Stultz wrote: > Hey Thomas, Ingo, > Here's my somewhat truncated queue for 4.6. I was hoping to > get the cross-timestamp patchset from Christopher sent along, > but he's got some last minute changes to address feedback from > Andy, so I'm holding off. > > If

Re: [patch 20/20] rcu: Make CPU_DYING_IDLE an explicit call

On Fri, 26 Feb 2016, Paul E. McKenney wrote: > > > --- a/kernel/cpu.c > > > +++ b/kernel/cpu.c > > > @@ -762,6 +762,7 @@ void cpuhp_report_idle_dead(void) > > > BUG_ON(st->state != CPUHP_AP_OFFLINE); > > > st->state = CPUHP_AP_IDLE_DEAD; > > > complete(>done); > > > > What prevents the

Re: [patch 20/20] rcu: Make CPU_DYING_IDLE an explicit call

On Fri, 26 Feb 2016, Paul E. McKenney wrote: > > > --- a/kernel/cpu.c > > > +++ b/kernel/cpu.c > > > @@ -762,6 +762,7 @@ void cpuhp_report_idle_dead(void) > > > BUG_ON(st->state != CPUHP_AP_OFFLINE); > > > st->state = CPUHP_AP_IDLE_DEAD; > > > complete(>done); > > > > What prevents the

Re: [PATCH v3 22/22] sound/usb: Use Media Controller API to share media resources

On Sat, 27 Feb 2016 03:55:39 +0100, Shuah Khan wrote: > > On 02/26/2016 01:50 PM, Takashi Iwai wrote: > > On Fri, 26 Feb 2016 21:08:43 +0100, > > Shuah Khan wrote: > >> > >> On 02/26/2016 12:55 PM, Takashi Iwai wrote: > >>> On Fri, 12 Feb 2016 00:41:38 +0100, > >>> Shuah Khan wrote: > >

Re: [PATCH v3 22/22] sound/usb: Use Media Controller API to share media resources

On Sat, 27 Feb 2016 03:55:39 +0100, Shuah Khan wrote: > > On 02/26/2016 01:50 PM, Takashi Iwai wrote: > > On Fri, 26 Feb 2016 21:08:43 +0100, > > Shuah Khan wrote: > >> > >> On 02/26/2016 12:55 PM, Takashi Iwai wrote: > >>> On Fri, 12 Feb 2016 00:41:38 +0100, > >>> Shuah Khan wrote: > >

Re: [patch 10/20] cpu/hotplug: Make target state writeable

Rafael, On Sat, 27 Feb 2016, Rafael J. Wysocki wrote: > On Friday, February 26, 2016 06:43:32 PM Thomas Gleixner wrote: > > Make it possible to write a target state to the per cpu state file, so we > > can > > switch between states. > > One thing that potentially may be problematic here is that

Re: [patch 10/20] cpu/hotplug: Make target state writeable

Rafael, On Sat, 27 Feb 2016, Rafael J. Wysocki wrote: > On Friday, February 26, 2016 06:43:32 PM Thomas Gleixner wrote: > > Make it possible to write a target state to the per cpu state file, so we > > can > > switch between states. > > One thing that potentially may be problematic here is that

Re: [PATCH v2 3/3] scsi: allow scsi devices to use direct complete

On Wed, Feb 24, 2016 at 04:22:28PM -0800, Derek Basehore wrote: > This allows scsi devices to remain runtime suspended for system > suspend. Since runtime suspend is stricter than system suspend > callbacks, this is just returning a positive number for the prepare > callback. AFAICT SCSI layer

Re: [PATCH v2 3/3] scsi: allow scsi devices to use direct complete

On Wed, Feb 24, 2016 at 04:22:28PM -0800, Derek Basehore wrote: > This allows scsi devices to remain runtime suspended for system > suspend. Since runtime suspend is stricter than system suspend > callbacks, this is just returning a positive number for the prepare > callback. AFAICT SCSI layer

Re: [PATCH v3 1/2] gpio: designware: switch device node to fwnode

在 2016/2/25 21:43, Andy Shevchenko 写道: > On Thu, Feb 25, 2016 at 1:58 PM, Jiang Qiu wrote: >> 在 2016/2/24 21:46, Andy Shevchenko 写道: >>> On Wed, Feb 24, 2016 at 2:33 PM, qiujiang wrote: > >>> - why do you use fwnode_*() instead of device_property_*()

Re: [PATCH v3 1/2] gpio: designware: switch device node to fwnode

在 2016/2/25 21:43, Andy Shevchenko 写道: > On Thu, Feb 25, 2016 at 1:58 PM, Jiang Qiu wrote: >> 在 2016/2/24 21:46, Andy Shevchenko 写道: >>> On Wed, Feb 24, 2016 at 2:33 PM, qiujiang wrote: > >>> - why do you use fwnode_*() instead of device_property_*() calls? >>> What prevents us to move to

Re: [PATCH] IPIP tunnel performance improvement

Yes, I did, but have no effect. I want to ask is, why David's patch not used. Thanks. Cong Wang said, at 2/27/2016 2:29 PM: > On Fri, Feb 26, 2016 at 8:40 PM, zhao ya wrote: >> From: Zhao Ya >> Date: Sat, 27 Feb 2016 10:06:44 +0800 >>

Re: [PATCH] IPIP tunnel performance improvement

Yes, I did, but have no effect. I want to ask is, why David's patch not used. Thanks. Cong Wang said, at 2/27/2016 2:29 PM: > On Fri, Feb 26, 2016 at 8:40 PM, zhao ya wrote: >> From: Zhao Ya >> Date: Sat, 27 Feb 2016 10:06:44 +0800 >> Subject: [PATCH] IPIP tunnel performance improvement

[PATCH v4 1/3] input: cygnus-update touchscreen dt node document

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support register access using syscon framework API's to take care of mutually exclusive access.In addition to this existing

[PATCH v4 1/3] input: cygnus-update touchscreen dt node document

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support register access using syscon framework API's to take care of mutually exclusive access.In addition to this existing

[PATCH v4 2/3] input: syscon support in bcm_iproc_tsc driver

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support register access using syscon framework API's to take care of mutually exclusive access. Signed-off-by: Raveendra

[PATCH v4 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touchscreen driver is enhanced to support syscon based register access to take care of mutually exclusive access. This patch enables syscon support in

[PATCH v4 2/3] input: syscon support in bcm_iproc_tsc driver

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support register access using syscon framework API's to take care of mutually exclusive access. Signed-off-by: Raveendra

[PATCH v4 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touchscreen driver is enhanced to support syscon based register access to take care of mutually exclusive access. This patch enables syscon support in

[PATCH v4 0/3] Syscon support for iProc touchscreen driver

This patchset is based on v4.5-rc3 tag and its tested on Broadcom Cygnus SoC. The patches can be fetched from iproc-tsc-v4 branch of https://github.com/Broadcom/arm64-linux.git Changes since v3: - Renamed touchscreen node "tsc" to "touchscreen" in dt binding document - Added support for syscon

[PATCH v4 0/3] Syscon support for iProc touchscreen driver

This patchset is based on v4.5-rc3 tag and its tested on Broadcom Cygnus SoC. The patches can be fetched from iproc-tsc-v4 branch of https://github.com/Broadcom/arm64-linux.git Changes since v3: - Renamed touchscreen node "tsc" to "touchscreen" in dt binding document - Added support for syscon

Re: [PATCH v4 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

On Fri, 26 Feb 2016, Darren Hart wrote: On Mon, Feb 22, 2016 at 10:29:48PM -0600, John Dahlstrom wrote: [...] Thank you for that information. One commit is sufficient to apply the patch to all kernel versions without fuzz: 4fa9dab ideapad_laptop: Lenovo G50-30 fix rfkill reports wireless

Re: [PATCH v4 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

On Fri, 26 Feb 2016, Darren Hart wrote: On Mon, Feb 22, 2016 at 10:29:48PM -0600, John Dahlstrom wrote: [...] Thank you for that information. One commit is sufficient to apply the patch to all kernel versions without fuzz: 4fa9dab ideapad_laptop: Lenovo G50-30 fix rfkill reports wireless

Re: [PATCH v2 1/3] input: cygnus-update touchscreen dt node document

Thanks Scott and Ray for the inputs. I will implement syscon only register access and send out the changes in patch set - v4. Regards, Raveendra On Tue, Feb 23, 2016 at 1:18 AM, Ray Jui wrote: > > > On 2/22/2016 11:41 AM, Scott Branden wrote: >> >> My comments below >> >>

Re: [PATCH v2 1/3] input: cygnus-update touchscreen dt node document

Thanks Scott and Ray for the inputs. I will implement syscon only register access and send out the changes in patch set - v4. Regards, Raveendra On Tue, Feb 23, 2016 at 1:18 AM, Ray Jui wrote: > > > On 2/22/2016 11:41 AM, Scott Branden wrote: >> >> My comments below >> >> On 16-02-22 11:36 AM,

Re: [RFC][PATCH v2 3/3] mm/zsmalloc: increase ZS_MAX_PAGES_PER_ZSPAGE

Hello Minchan, sorry for very long reply. On (02/24/16 01:05), Minchan Kim wrote: [..] > > And the thing is -- quite huge internal class fragmentation. These are the > > 'normal' > > classes, not affected by ORDER modification in any way: > > > > class size almost_full almost_empty

Re: [RFC][PATCH v2 3/3] mm/zsmalloc: increase ZS_MAX_PAGES_PER_ZSPAGE

Hello Minchan, sorry for very long reply. On (02/24/16 01:05), Minchan Kim wrote: [..] > > And the thing is -- quite huge internal class fragmentation. These are the > > 'normal' > > classes, not affected by ORDER modification in any way: > > > > class size almost_full almost_empty

Re: [PATCH] IPIP tunnel performance improvement

On Fri, Feb 26, 2016 at 8:40 PM, zhao ya wrote: > From: Zhao Ya > Date: Sat, 27 Feb 2016 10:06:44 +0800 > Subject: [PATCH] IPIP tunnel performance improvement > > bypass the logic of each packet's own neighbour creation when using >

Re: [PATCH] IPIP tunnel performance improvement

On Fri, Feb 26, 2016 at 8:40 PM, zhao ya wrote: > From: Zhao Ya > Date: Sat, 27 Feb 2016 10:06:44 +0800 > Subject: [PATCH] IPIP tunnel performance improvement > > bypass the logic of each packet's own neighbour creation when using > pointopint or loopback device. > > Recently, in our tests, met

Re: [PATCH v4 1/5] getcpu_cache system call: cache CPU number of running thread

On 02/26/16 16:40, Mathieu Desnoyers wrote: I think it would be a good idea to make this a general pointer for the kernel to be able to write per thread state to user space, which obviously can't be done with the vDSO. This means the libc per thread startup should query the kernel for the size

Re: [PATCH v4 1/5] getcpu_cache system call: cache CPU number of running thread

On 02/26/16 16:40, Mathieu Desnoyers wrote: I think it would be a good idea to make this a general pointer for the kernel to be able to write per thread state to user space, which obviously can't be done with the vDSO. This means the libc per thread startup should query the kernel for the size

[PATCH] mm/zsmalloc: add compact column to pool stat

Add a new column to pool stats, which will tell us class' zs_can_compact() number, so it will be easier to analyze zsmalloc fragmentation. At the moment, we have only numbers of FULL and ALMOST_EMPTY classes, but they don't tell us how badly the class is fragmented internally. The new

[PATCH] mm/zsmalloc: add compact column to pool stat

Add a new column to pool stats, which will tell us class' zs_can_compact() number, so it will be easier to analyze zsmalloc fragmentation. At the moment, we have only numbers of FULL and ALMOST_EMPTY classes, but they don't tell us how badly the class is fragmented internally. The new

[PATCH v6 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

Some Lenovo ideapad models lack a physical rfkill switch. On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK, ideapad-laptop would wrongly report all radios as blocked by hardware which caused wireless network connections to fail. Add these models without an rfkill switch to the

[PATCH v6 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list

Some Lenovo ideapad models lack a physical rfkill switch. On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK, ideapad-laptop would wrongly report all radios as blocked by hardware which caused wireless network connections to fail. Add these models without an rfkill switch to the

[net-next][PATCH 03/13] MAINTAINERS: update RDS entry

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

[net-next][PATCH 01/13] RDS: Drop stale iWARP RDMA transport

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

[net-next][PATCH 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages

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

[net-next][PATCH 03/13] MAINTAINERS: update RDS entry

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 355e1c8..9d79bea 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9081,10 +9081,14 @@ S:

[net-next][PATCH 01/13] RDS: Drop stale iWARP RDMA transport

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

[net-next][PATCH 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages

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

[net-next][PATCH 05/13] RDS: IB: Re-organise ibmr code

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

[net-next][PATCH 05/13] RDS: IB: Re-organise ibmr code

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

[net-next][PATCH 11/13] RDS: IB: add Fastreg MR (FRMR) detection support

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. Using module parameter 'prefer_frmr', user can choose its preferred MR method for RDS.

[net-next][PATCH 09/13] RDS: IB: handle the RDMA CM time wait event

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-next][PATCH 00/13] RDS: Major clean-up with couple of new features for 4.6

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. Brief summary of the series: - Drop the stale iWARP support: RDS iWarp support code has become stale and non testable for

[net-next][PATCH 10/13] RDS: IB: add mr reused stats

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

[net-next][PATCH 11/13] RDS: IB: add Fastreg MR (FRMR) detection support

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. Using module parameter 'prefer_frmr', user can choose its preferred MR method for RDS.

[net-next][PATCH 09/13] RDS: IB: handle the RDMA CM time wait event

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

[net-next][PATCH 00/13] RDS: Major clean-up with couple of new features for 4.6

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. Brief summary of the series: - Drop the stale iWARP support: RDS iWarp support code has become stale and non testable for

[net-next][PATCH 10/13] RDS: IB: add mr reused stats

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

[net-next][PATCH 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode

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 RDS to have RDS functional on them. Some of the older HCAs support both FMR and

[net-next][PATCH 12/13] RDS: IB: allocate extra space on queues for FRMR support

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-next][PATCH 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode

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 RDS to have RDS functional on them. Some of the older HCAs support both FMR and FRMR modes. So to try out

[net-next][PATCH 12/13] RDS: IB: allocate extra space on queues for FRMR support

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-next][PATCH 08/13] RDS: IB: add connection info to ibmr

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

[net-next][PATCH 08/13] RDS: IB: add connection info to ibmr

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

[net-next][PATCH 07/13] RDS: IB: move FMR code to its own file

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 | 105

[net-next][PATCH 07/13] RDS: IB: move FMR code to its own file

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 | 105 ++--- 3 files changed, 133

[net-next][PATCH 06/13] RDS: IB: create struct rds_ib_fmr

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-next][PATCH 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency

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-next][PATCH 06/13] RDS: IB: create struct rds_ib_fmr

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,

[net-next][PATCH 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency

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 +++---

Re: [PATCH] IPIP tunnel performance improvement

BTW,before the version 3.5 kernel, the source code contains the logic. 2.6.32, for example, in arp_bind_neighbour function, there are the following logic: __be32 nexthop = ((struct rtable *) DST) - > rt_gateway; if (dev - > flags & (IFF_LOOPBACK | IFF_POINTOPOINT)) nexthop = 0; n =

Re: [PATCH] IPIP tunnel performance improvement

BTW,before the version 3.5 kernel, the source code contains the logic. 2.6.32, for example, in arp_bind_neighbour function, there are the following logic: __be32 nexthop = ((struct rtable *) DST) - > rt_gateway; if (dev - > flags & (IFF_LOOPBACK | IFF_POINTOPOINT)) nexthop = 0; n =

[PATCH] IPIP tunnel performance improvement

From: Zhao Ya Date: Sat, 27 Feb 2016 10:06:44 +0800 Subject: [PATCH] IPIP tunnel performance improvement bypass the logic of each packet's own neighbour creation when using pointopint or loopback device. Recently, in our tests, met a performance problem. In a large

[PATCH] IPIP tunnel performance improvement

From: Zhao Ya Date: Sat, 27 Feb 2016 10:06:44 +0800 Subject: [PATCH] IPIP tunnel performance improvement bypass the logic of each packet's own neighbour creation when using pointopint or loopback device. Recently, in our tests, met a performance problem. In a large number of packets with

RE: [PATCH 5/5] hv: Track allocations of children of hv_vmbus in private resource tree

> -Original Message- > From: KY Srinivasan > Sent: Friday, February 26, 2016 5:09 PM > To: Jake Oshins ; linux-...@vger.kernel.org; > gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; >

RE: [PATCH 5/5] hv: Track allocations of children of hv_vmbus in private resource tree

> -Original Message- > From: KY Srinivasan > Sent: Friday, February 26, 2016 5:09 PM > To: Jake Oshins ; linux-...@vger.kernel.org; > gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; > vkuzn...@redhat.com; Haiyang

Re: [RFC/RFT][PATCH v4 1/2] cpufreq: New governor using utilization data from the scheduler

On 02/25/2016 01:14 PM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Add a new cpufreq scaling governor, called "schedutil", that uses > scheduler-provided CPU utilization information as input for making > its decisions. > > Doing that is possible after

Re: [RFC/RFT][PATCH v4 1/2] cpufreq: New governor using utilization data from the scheduler

On 02/25/2016 01:14 PM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Add a new cpufreq scaling governor, called "schedutil", that uses > scheduler-provided CPU utilization information as input for making > its decisions. > > Doing that is possible after commit fe7034338ba0 (cpufreq:

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

On 02/26/2016 06:39 PM, Rafael J. Wysocki wrote: >>> One thing I personally like in the RCU-based approach is its universality. >>> The >>> callbacks may be installed by different entities in a uniform way: >>> intel_pstate >>> can do that, the old governors can do that, my experimental

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

On 02/26/2016 06:39 PM, Rafael J. Wysocki wrote: >>> One thing I personally like in the RCU-based approach is its universality. >>> The >>> callbacks may be installed by different entities in a uniform way: >>> intel_pstate >>> can do that, the old governors can do that, my experimental

Re: [PATCH v12 4/5] arm64, numa: Add NUMA support for arm64 platforms.

On Sat, Feb 27, 2016 at 1:21 AM, David Daney wrote: > On 02/26/2016 10:53 AM, Will Deacon wrote: > [...] >>> >>> diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c >>> new file mode 100644 >>> index 000..604e886 >>> --- /dev/null >>> +++ b/arch/arm64/mm/numa.c

Re: [PATCH v12 4/5] arm64, numa: Add NUMA support for arm64 platforms.

On Sat, Feb 27, 2016 at 1:21 AM, David Daney wrote: > On 02/26/2016 10:53 AM, Will Deacon wrote: > [...] >>> >>> diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c >>> new file mode 100644 >>> index 000..604e886 >>> --- /dev/null >>> +++ b/arch/arm64/mm/numa.c >>> @@ -0,0 +1,403 @@ > >

Re: [PATCH] printk/nmi: restore printk_func in nmi_panic

On (02/27/16 12:09), Sergey Senozhatsky wrote: > On (02/27/16 11:19), Sergey Senozhatsky wrote: > [..] > > > I think about a compromise. We should try to get the messages > > > out only when kdump is not enabled. > > > > can we zap_locks() if we are on > >

Re: [PATCH] printk/nmi: restore printk_func in nmi_panic

On (02/27/16 12:09), Sergey Senozhatsky wrote: > On (02/27/16 11:19), Sergey Senozhatsky wrote: > [..] > > > I think about a compromise. We should try to get the messages > > > out only when kdump is not enabled. > > > > can we zap_locks() if we are on > >

Re: [PATCH V2 11/12] net-next: mediatek: add Kconfig and Makefile

Hi John, [auto build test ERROR on net/master] [also build test ERROR on v4.5-rc5 next-20160226] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/John-Crispin/net-next-mediatek-add-ethernet

Re: [PATCH V2 11/12] net-next: mediatek: add Kconfig and Makefile

Hi John, [auto build test ERROR on net/master] [also build test ERROR on v4.5-rc5 next-20160226] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/John-Crispin/net-next-mediatek-add-ethernet

[PATCH 1/2] clocksource: introduce clocksource_freq2mult()

From: Alexander Kuleshov The clocksource_khz2mult() and clocksource_hz2mult() share similar code wihch calculates a mult from the given frequency. Both implementations in differ only in value of a frequency. This patch introduces the clocksource_freq2mult() helper with

[PATCH 1/2] clocksource: introduce clocksource_freq2mult()

From: Alexander Kuleshov The clocksource_khz2mult() and clocksource_hz2mult() share similar code wihch calculates a mult from the given frequency. Both implementations in differ only in value of a frequency. This patch introduces the clocksource_freq2mult() helper with generic implementation of

Re: [PATCH net-next 7/9] net: dsa: mv88e6xxx: restore VLANTable map control

On Fri, Feb 26, 2016 at 10:47:38PM +, Kevin Smith wrote: > Hi Andrew, > > On 02/26/2016 04:35 PM, Andrew Lunn wrote: > > On Fri, Feb 26, 2016 at 10:12:28PM +, Kevin Smith wrote: > >> Hi Vivien, Andrew, > >> > >> On 02/26/2016 03:37 PM, Vivien Didelot wrote: > >>> Here, 5 is the CPU port

Re: [PATCH net-next 7/9] net: dsa: mv88e6xxx: restore VLANTable map control

On Fri, Feb 26, 2016 at 10:47:38PM +, Kevin Smith wrote: > Hi Andrew, > > On 02/26/2016 04:35 PM, Andrew Lunn wrote: > > On Fri, Feb 26, 2016 at 10:12:28PM +, Kevin Smith wrote: > >> Hi Vivien, Andrew, > >> > >> On 02/26/2016 03:37 PM, Vivien Didelot wrote: > >>> Here, 5 is the CPU port

[PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

Hey Thomas, Ingo, Here's my somewhat truncated queue for 4.6. I was hoping to get the cross-timestamp patchset from Christopher sent along, but he's got some last minute changes to address feedback from Andy, so I'm holding off. If the response is good for that last change, I may try to send

[PATCH 2/2] jiffies: use CLOCKSOURCE_MASK instead of constant

From: Alexander Kuleshov The CLOCKSOURCE_MASK(32) macro expands to the same value, but makes code more readable. Cc: Thomas Gleixner Cc: Prarit Bhargava Cc: Richard Cochran Cc: Ingo Molnar

[PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6

Hey Thomas, Ingo, Here's my somewhat truncated queue for 4.6. I was hoping to get the cross-timestamp patchset from Christopher sent along, but he's got some last minute changes to address feedback from Andy, so I'm holding off. If the response is good for that last change, I may try to send

[PATCH 2/2] jiffies: use CLOCKSOURCE_MASK instead of constant

From: Alexander Kuleshov The CLOCKSOURCE_MASK(32) macro expands to the same value, but makes code more readable. Cc: Thomas Gleixner Cc: Prarit Bhargava Cc: Richard Cochran Cc: Ingo Molnar Signed-off-by: Alexander Kuleshov Signed-off-by: John Stultz --- kernel/time/jiffies.c | 2 +- 1

Re: [PATCH] printk/nmi: restore printk_func in nmi_panic

On (02/27/16 11:19), Sergey Senozhatsky wrote: [..] > > I think about a compromise. We should try to get the messages > > out only when kdump is not enabled. > > can we zap_locks() if we are on > nmi_panic()->panic()->console_flush_on_panic() path? > console_flush_on_panic() is happening after

Re: [PATCH] printk/nmi: restore printk_func in nmi_panic

On (02/27/16 11:19), Sergey Senozhatsky wrote: [..] > > I think about a compromise. We should try to get the messages > > out only when kdump is not enabled. > > can we zap_locks() if we are on > nmi_panic()->panic()->console_flush_on_panic() path? > console_flush_on_panic() is happening after

Re: [PATCH v3 22/22] sound/usb: Use Media Controller API to share media resources

On 02/26/2016 01:50 PM, Takashi Iwai wrote: > On Fri, 26 Feb 2016 21:08:43 +0100, > Shuah Khan wrote: >> >> On 02/26/2016 12:55 PM, Takashi Iwai wrote: >>> On Fri, 12 Feb 2016 00:41:38 +0100, >>> Shuah Khan wrote: Change ALSA driver to use Media Controller API to share media

Re: [PATCH v3 22/22] sound/usb: Use Media Controller API to share media resources

On 02/26/2016 01:50 PM, Takashi Iwai wrote: > On Fri, 26 Feb 2016 21:08:43 +0100, > Shuah Khan wrote: >> >> On 02/26/2016 12:55 PM, Takashi Iwai wrote: >>> On Fri, 12 Feb 2016 00:41:38 +0100, >>> Shuah Khan wrote: Change ALSA driver to use Media Controller API to share media

Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles

On Fri, Feb 26, 2016 at 11:26:02PM +0800, Chen Gang wrote: > > As for coding style, actually IMHO this patch is even _not_ a coding > > style, more like a code shuffle, indeed. > > > > "80 column limitation" is about coding style, I guess, all of us agree > with it. No, it's been accepted that

Re: [PATCH trivial] include/linux/gfp.h: Improve the coding styles

On Fri, Feb 26, 2016 at 11:26:02PM +0800, Chen Gang wrote: > > As for coding style, actually IMHO this patch is even _not_ a coding > > style, more like a code shuffle, indeed. > > > > "80 column limitation" is about coding style, I guess, all of us agree > with it. No, it's been accepted that

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

On Thursday, February 25, 2016 04:34:23 PM Steve Muckle wrote: > On 02/24/2016 07:55 PM, Rafael J. Wysocki wrote: > > Hi, [cut] > > One thing I personally like in the RCU-based approach is its universality. > > The > > callbacks may be installed by different entities in a uniform way: > >

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

On Thursday, February 25, 2016 04:34:23 PM Steve Muckle wrote: > On 02/24/2016 07:55 PM, Rafael J. Wysocki wrote: > > Hi, [cut] > > One thing I personally like in the RCU-based approach is its universality. > > The > > callbacks may be installed by different entities in a uniform way: > >

  1   2   3   4   5   6   7   8   9   10   >