Re: [PATCH] mm: free reserved area's memmap if possiable

2017-02-13 Thread zhouxianrong
if the reserved area by user were so big which caused the memmap big, and the reserved area's memamp did not be used by kernel, then user could free the the reserved area's memamp by memblock_mark_raw_pfn interface which is added by me. On 2017/2/14 14:53, zhouxianr...@huawei.com wrote: From: zh

[PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c index 864e673..18

[PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index 253310c..a4cb966 100644 --- a/drivers/v

[PATCH v3 3/9] raid5: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/raid5.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 36c13e4..22a0326 100644 --- a/drivers/md/raid5.c ++

[PATCH v3 0/9] Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Change from v2 - replace for_each(wake_list) with the safe version in scheduler. - fix a trivial comment in llist.h Change from v1 - split one patch to several ones, one for each subsystem. - replace for_each with the safe version where it's necessary. Byungchul Park (9): llist: Provide a safe

[PATCH v3 1/9] llist: Provide a safe version for llist_for_each

2017-02-13 Thread Byungchul Park
Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park --- include/linux/lli

[PATCH v3 6/9] namespace.c: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 --- a/fs/namespace.c +++ b/fs/na

[PATCH v3 9/9] mm: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@

[PATCH v3 5/9] fput: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644 --- a/fs/file_table.c +++ b/f

[PATCH v3 8/9] sched: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/sched/core.c | 15 +++ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index d01f9d0..8938125 100644 --- a/kernel/

[PATCH v3 7/9] irq_work: Don't reinvent the wheel but use existing llist API

2017-02-13 Thread Byungchul Park
Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 --- a/kernel/irq_work.c +++ b/k

RE: [tip:locking/core] refcount_t: Introduce a special purpose refcount type

2017-02-13 Thread Reshetova, Elena
> Subject: refcount: Out-of-line everything > From: Peter Zijlstra > Date: Fri Feb 10 16:27:52 CET 2017 > > Linus asked to please make this real C code. Perhaps a completely stupid question, but I am going to ask anyway since only this way I can learn. What a real difference it makes? Or are we

Re: [PATCH v2] tags: honor COMPILED_SOURCE with apart output directory

2017-02-13 Thread Robert Jarzmik
Robert Jarzmik writes: > Robert Jarzmik writes: >> Signed-off-by: Robert Jarzmik >> --- >> Since v1: amended k expression, Marek's comments > Hi Marek, > > Is this version good for you ? Marek, could you take a look please ? -- Robert >> --- >> scripts/tags.sh | 3 ++- >> 1 file changed, 2 i

Re: [PATCH v3 1/9] llist: Provide a safe version for llist_for_each

2017-02-13 Thread Huang, Ying
Byungchul Park writes: > Sometimes we have to dereference next field of llist node before entering > loop becasue the node might be deleted or the next field might be > modified within the loop. So this adds the safe version of llist_for_each, > that is, llist_for_each_safe. > > Signed-off-by: By

Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM

2017-02-13 Thread Marek Szyprowski
Hi Vinod, On 2017-02-13 16:47, Vinod Koul wrote: On Mon, Feb 13, 2017 at 04:32:32PM +0100, Ulf Hansson wrote: [...] Although, I don't know of other examples, besides the runtime PM use case, where non-atomic channel prepare/unprepare would make sense. Do you? The primary ask for that has be

<    5   6   7   8   9   10