Hello Joonsoo,
On Tue, Apr 09, 2013 at 10:21:16AM +0900, Joonsoo Kim wrote:
> In shrink_(in)active_list(), we can fail to put into lru, and these pages
> are reclaimed accidentally. Currently, these pages are not counted
> for sc->nr_reclaimed, but with this information, we can stop to reclaim
>
Hi Dan,
Thank you for the patch.
We are also trying to fix the issue:
https://lkml.org/lkml/2013/2/19/29
https://lkml.org/lkml/2013/4/8/55
and the fix is finally in Greg's tty git tree since yesterday:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
(tty-linus branch).
Best
2013/4/8 John W. Linville :
> Please consider this set of fixes for the 3.9 stream...
>
(...)
>
> Please let me know if there are problems!
John, could you take a look at what has happened to the
[PATCH V2] ssb: implement spurious tone avoidance
?
Message-Id:
On Mon, Apr 08, 2013 at 03:47:35PM -0600, Toshi Kani wrote:
> Added release_mem_region_adjustable(), which releases a requested
> region from a currently busy memory resource. This interface
> adjusts the matched memory resource accordingly even if the
> requested region does not match exactly
Hi Cody,
On 04/09/2013 01:39 AM, Cody P Schafer wrote:
On 04/06/2013 06:37 PM, Simon Jeons wrote:
Hi Cody,
On 04/06/2013 04:33 AM, Cody P Schafer wrote:
Creates pageset_set_batch() for use in setup_pageset().
pageset_set_batch() imitates the functionality of
setup_pagelist_highmark(), but uses
Hi Minchan,
On 04/09/2013 09:02 AM, Minchan Kim wrote:
Hi Andrew,
On Mon, Apr 08, 2013 at 02:17:10PM -0700, Andrew Morton wrote:
On Mon, 8 Apr 2013 15:01:02 +0900 Minchan Kim wrote:
Swap subsystem does lazy swap slot free with expecting the page
would be swapped out again so we can avoid
Hi Rui,
On Tue, Apr 2, 2013 at 3:56 PM, Kukjin Kim wrote:
> Amit Daniel Kachhap wrote:
>>
>> This patchset adds TMU(Thermal management Unit) driver support for
>> exynos5440 platform. There are 3 instances of the TMU controllers so
>> necessary cleanup is done to handle multiple thermal zone.
>>
There were a couple signedness bugs decrementing "i" which would lead to
a forever loops.
I've made a couple other variables signed as well because they are all
related array offsets and it would be weird if they weren't the same
type.
Signed-off-by: Dan Carpenter
diff --git
Hi Tang,
The patch works well on my x86_64 box.
I confirmed that hotpluggable node is allocated as Movable Zone.
So feel free to add:
Tested by: Yasuaki Ishimatsu
Nitpick below.
2013/04/05 18:39, Tang Chen wrote:
> Before this patch-set, we introduced movablemem_map boot option which allowed
On 04/02/2013 11:23 AM, Alex Shi wrote:
> This version resolved the aim7 liked benchmark issue by patch 8th.
> Thanks for MikeG's avg_idle that is a good bursty wakeup indicator.
>
> The first 3 patches were also include in my power aware scheduling patchset.
>
> Morten, you can rebase your
On Mon, Apr 08, 2013 at 08:27:50PM -0700, John Stultz wrote:
> On 04/08/2013 07:18 PM, Minchan Kim wrote:
> >On Mon, Apr 08, 2013 at 05:36:42PM -0700, John Stultz wrote:
> >>On 04/07/2013 05:46 PM, Minchan Kim wrote:
> >>>Hello John,
> >>>
> >>>As you know, userland people wanted to handle vrange
On Mon, Apr 08, 2013 at 12:05:52PM -0700, John Stultz wrote:
>
> So thinking this through further, I'm worried we may _not_ be able
> to eventually enable this to be a vdso as I had earlier hoped.
> Mostly because I'm not sure how the fd -> file -> clock lookup could
> be done in userland (any
On 04/08/2013 06:00 PM, Peter Zijlstra wrote:
> On Mon, 2013-03-25 at 13:24 +0800, Michael Wang wrote:
>> if (affine_sd) {
>> - if (cpu != prev_cpu && wake_affine(affine_sd, p,
>> sync))
>> + if (cpu != prev_cpu && wake_affine(affine_sd, p,
>> sync)) {
>> +
On Thu, Apr 04, 2013 at 04:18:01PM -0600, Bjorn Helgaas wrote:
> On Wed, Mar 13, 2013 at 5:27 PM, Yinghai Lu wrote:
> > From: Ram Pai
> >
> > Currently pci_dev structure holds an array of 17 PCI resources; six base
> > BARs, one ROM BAR, four BRIDGE BARs, six sriov BARs. This is wasteful.
> > A
On Tue, Apr 9, 2013 at 3:43 AM, Andrew Morton wrote:
>
> Fair enough. I'd go futher...
>
> From: Andrew Morton
> Subject: auditsc-use-kzalloc-instead-of-kmallocmemset-fix
>
> remove audit_set_context() altogether - fold it into its caller
>
> Cc: Al Viro
> Cc: Eric Paris
> Cc: Rakib Mullick
Make space before semicolon a warning instead
of a --strict CHK test.
Signed-off-by: Joe Perches
---
>> There's no specific CodingStyle violation here
> Let's fix CodingStyle then?
I'll leave that bit for you...
scripts/checkpatch.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Quoting Stephen Warren (2013-04-04 10:53:40)
> On 04/04/2013 11:48 AM, Peter De Schrijver wrote:
> > The device tree binding models Tegra114 CAR (Clock And Reset) as a single
> > monolithic clock provider.
> >
> > --
> >
> > Mike,
> >
> > This is a small binding doc update only. Hence I didn't
On Mon, 08 Apr 2013 20:18:20 -0700 Joe Perches wrote:
> On Mon, 2013-04-08 at 20:10 -0700, Andrew Morton wrote:
> > > --- a/lib/bitmap.c
> []
> > > + for (i = 0 ; i < nlongs_reg ; i++) {
> >
> > No space before the semicolon, please. checkpatch should warn about
> > this but it seems to be
(2013/04/08 17:23), Li Zefan wrote:
> Now memcg uses cgroup->id instead of css_id. Update some comments and
> set mem_cgroup_subsys->use_id to 0.
>
> Signed-off-by: Li Zefan
Acked-by: KAMEZAWA Hiroyuki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On 8 April 2013 22:29, Steven Rostedt wrote:
> Looks like Amit was left off the patch 0, and missed the power savings
> explanation that you did there. Perhaps you should have included that in
> each patch change log.
He isn't supposed to miss any of my emails, he is my manager :)
Don't know if
(2013/04/08 17:20), Li Zefan wrote:
> This will be used as a replacement for css_lookup().
>
> Signed-off-by: Li Zefan
> ---
> include/linux/cgroup.h | 1 +
> kernel/cgroup.c| 31 +--
> 2 files changed, 26 insertions(+), 6 deletions(-)
>
> diff --git
(2013/04/08 17:22), Li Zefan wrote:
> This is a preparation to kill css_id.
>
> Signed-off-by: Li Zefan
Acked-by: KAMEZAWA Hiroyuki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
(2013/04/08 17:21), Li Zefan wrote:
> This is a preparation to kill css_id.
>
> Signed-off-by: Li Zefan
> ---
> mm/memcontrol.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Acked-by: KAMEZAWA Hiroyoku
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, Apr 09, 2013 at 11:18:21AM +0800, Li Zefan wrote:
> >> - if (memcg->memcg_name)
> >> - seq_printf(m, "%s:\n", memcg->memcg_name);
> >> + ret = cgroup_path(memcg->css.cgroup, memcg_name, PAGE_SIZE);
> >> + if (!ret)
> >> +
(2013/04/08 17:21), Li Zefan wrote:
> This is a preparation to kill css_id.
>
> Signed-off-by: Li Zefan
> ---
> mm/memcontrol.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 5aa6e91..14f1375 100644
> --- a/mm/memcontrol.c
>
(2013/04/08 17:20), Li Zefan wrote:
> This will be used as a replacement for css_lookup().
>
> Signed-off-by: Li Zefan
> ---
> include/linux/cgroup.h | 1 +
> kernel/cgroup.c| 31 +--
> 2 files changed, 26 insertions(+), 6 deletions(-)
>
> diff --git
On 9 April 2013 09:15, Joe Perches wrote:
> On Tue, 2013-04-09 at 09:06 +0530, Sachin Kamat wrote:
>> On 9 April 2013 08:39, Joe Perches wrote:
>> > On Tue, 2013-04-09 at 08:33 +0530, Sachin Kamat wrote:
>> >> On 13 March 2013 14:42, Sachin Kamat wrote:
>> >> > Fixes the following warnings:
>>
(2013/04/09 12:18), Li Zefan wrote:
>>> @@ -5188,12 +5154,28 @@ static int mem_cgroup_dangling_read(struct cgroup
>>> *cont, struct cftype *cft,
>>> struct seq_file *m)
>>>{
>>> struct mem_cgroup *memcg;
>>> + char *memcg_name;
>>> + int ret;
>>> +
On Tue, 2013-04-09 at 09:06 +0530, Sachin Kamat wrote:
> On 9 April 2013 08:39, Joe Perches wrote:
> > On Tue, 2013-04-09 at 08:33 +0530, Sachin Kamat wrote:
> >> On 13 March 2013 14:42, Sachin Kamat wrote:
> >> > Fixes the following warnings:
> >> > WARNING: line over 80 characters
> >> >
Hey Thomas,
Here's the second chunk of my 3.10 timekeeping changes.
This queue includes:
* NTP locking changes needed for your shadow-timekeeping work
* Your shadow-timekeeping work
* hrtimer fixes from David and Prarit (also tagged for stable)
Let me know if you have any comments or
On Mon, Apr 8, 2013 at 8:25 PM, Dave Young wrote:
> I have another question, under x86_64 consider 1st kernel memory < 4G,
> is the swiotlb memory still necessary?
No. unless use swiotlb=force.
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 9 April 2013 08:39, Joe Perches wrote:
> On Tue, 2013-04-09 at 08:33 +0530, Sachin Kamat wrote:
>> On 13 March 2013 14:42, Sachin Kamat wrote:
>> > Fixes the following warnings:
>> > WARNING: line over 80 characters
>> > WARNING: Prefer pr_warn(... to pr_warning(...
>> > diff --git
David Cohen writes:
> openssl may send garbage to stderr when generating X.509 key pair for
> modules signature regardless there was an error or not. It makes more
> difficult to create scripts based on kernel error/warning messages.
> This patch makes sure openssl logs go to default stdout.
>
>
On 2013/4/9 11:21, Kamezawa Hiroyuki wrote:
> (2013/04/08 17:20), Li Zefan wrote:
>> This will be used as a replacement for css_is_ancestor().
>>
>> Signed-off-by: Li Zefan
>
> Acked-by: KAMEZAWA Hiroyuki
>
> Hmmbut do we need "depth" ?
>
which was removed in Tejun's
"[PATCHSET] perf,
On 04/08/2013 07:18 PM, Minchan Kim wrote:
On Mon, Apr 08, 2013 at 05:36:42PM -0700, John Stultz wrote:
On 04/07/2013 05:46 PM, Minchan Kim wrote:
Hello John,
As you know, userland people wanted to handle vrange with mmaped
pointer rather than fd-based and see the SIGBUS so I thought more
On 04/09/2013 02:37 AM, Yinghai Lu wrote:
> On Mon, Apr 8, 2013 at 12:09 AM, Dave Young wrote:
>>> We have now modified crashkernel=X to allocate memory beyong 4G (if
>>> available) and do not allocate low range for crashkernel if the user
>>> does not specify that with crashkernel_low=Y. This
(2013/04/08 17:20), Li Zefan wrote:
> This will be used as a replacement for css_is_ancestor().
>
> Signed-off-by: Li Zefan
Acked-by: KAMEZAWA Hiroyuki
Hmmbut do we need "depth" ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
>> @@ -5188,12 +5154,28 @@ static int mem_cgroup_dangling_read(struct cgroup
>> *cont, struct cftype *cft,
>> struct seq_file *m)
>> {
>> struct mem_cgroup *memcg;
>> +char *memcg_name;
>> +int ret;
>> +
>> +/*
>> + * cgroup.c will do
On Mon, 2013-04-08 at 20:10 -0700, Andrew Morton wrote:
> > --- a/lib/bitmap.c
[]
> > + for (i = 0 ; i < nlongs_reg ; i++) {
>
> No space before the semicolon, please. checkpatch should warn about
> this but it seems to be broken.
There's no specific CodingStyle violation here
Adding --strict
On 2013/4/8 23:43, Tejun Heo wrote:
> On Mon, Apr 08, 2013 at 04:20:59PM +0800, Li Zefan wrote:
>> +/**
>> + * cgroup_from_id - lookup cgroup by id
>> + * @ss: cgroup subsys to be looked into.
>> + * @id: the id
>> + *
>> + * Returns pointer to cgroup if there is valid one with id.
>> + * NULL if
(2013/04/08 15:36), Li Zefan wrote:
> Now memcg has the same life cycle as its corresponding cgroup,
> we don't have to save the cgroup path name in memcg->memcg_name.
>
> Signed-off-by: Li Zefan
> ---
> mm/memcontrol.c | 65
> +
> 1
On Tue, 9 Apr 2013 11:44:46 +0900 Chanho Min wrote:
> If bitmap_find_free_region() is called with order=0, We can reduce
> for-loops to find 1 free bit. First, It scans bitmap array by the
> increment of long type, then find 1 free bit within 1 long type value.
>
> In 32 bits system and 1024
On Tue, 2013-04-09 at 08:33 +0530, Sachin Kamat wrote:
> On 13 March 2013 14:42, Sachin Kamat wrote:
> > Fixes the following warnings:
> > WARNING: line over 80 characters
> > WARNING: Prefer pr_warn(... to pr_warning(...
> > diff --git a/drivers/irqchip/exynos-combiner.c
> >
Hello Ted,
- Original Message -
> From: "Theodore Ts'o"
> To: "Eric Whitney"
> Cc: "Dmitry Monakhov" , "Christian Kujau"
> , "CAI Qian"
> , "LKML" , "linux-s390"
> , "Steve Best"
> , linux-e...@vger.kernel.org
> Sent: Wednesday, April 3, 2013 10:41:14 PM
> Subject: Re: [PATCH] ext4:
Hi Kukjin,
On 13 March 2013 14:42, Sachin Kamat wrote:
> Fixes the following warnings:
> WARNING: line over 80 characters
> WARNING: Prefer pr_warn(... to pr_warning(...
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/irqchip/exynos-combiner.c |6 --
> 1 files changed, 4 insertions(+),
On 2013/4/8 22:57, Michal Hocko wrote:
> On Mon 08-04-13 16:22:11, Li Zefan wrote:
>> This is a preparation to kill css_id.
>>
>> Signed-off-by: Li Zefan
>
> This patch depends on the following patch, doesn't it? There is no
> guarantee that id fits into short right now. Not such a big deal but
On 2013/4/8 22:53, Michal Hocko wrote:
> On Mon 08-04-13 16:21:29, Li Zefan wrote:
>> This is a preparation to kill css_id.
>>
>> Signed-off-by: Li Zefan
>
> I would be tempted to stuff this into the same patch which introduces
> cgroup_from_id but this is just a minor thing.
>
yeah it's not a
(2013/04/08 15:36), Li Zefan wrote:
> Now memcg has the same life cycle with its corresponding cgroup, and
> a cgroup is freed via RCU and then mem_cgroup_css_free() is called
> in a work function, so we can simply call __mem_cgroup_free() in
> mem_cgroup_css_free().
>
> This actually reverts
(2013/04/08 15:34), Li Zefan wrote:
> Use css_get/put instead of mem_cgroup_get/put.
>
> We can't do a simple replacement, because here mem_cgroup_put()
> is called during mem_cgroup_css_free(), while mem_cgroup_css_free()
> won't be called until css refcnt goes down to 0.
>
> Instead we
(2013/04/08 15:34), Li Zefan wrote:
> Use css_get()/css_put() instead of mem_cgroup_get()/mem_cgroup_put().
>
> There are two things being done in the current code:
>
> First, we acquired a css_ref to make sure that the underlying cgroup
> would not go away. That is a short lived reference, and
(2013/04/08 15:33), Li Zefan wrote:
> From: Michal Hocko
>
> mem_cgroup_css_online calls mem_cgroup_put if memcg_init_kmem
> fails. This is not correct because only memcg_propagate_kmem takes an
> additional reference while mem_cgroup_sockets_init is allowed to fail as
> well (although no
(2013/04/08 15:33), Li Zefan wrote:
> From: Michal Hocko
>
> This reverts commit e4715f01be697a3730c78f8b595591d6a88c
>
> mem_cgroup_put is hierarchy aware so mem_cgroup_put(memcg) already drops
> an additional reference from all parents so the additional
> mem_cgrroup_put(parent)
namebuf is NUL terminated string. better always let it ended by '\0'.
ownername and module_name(owner) are the same buf len. strcpy is better.
Signed-off-by: Chen Gang
---
kernel/module.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/module.c
If bitmap_find_free_region() is called with order=0, We can reduce
for-loops to find 1 free bit. First, It scans bitmap array by the
increment of long type, then find 1 free bit within 1 long type value.
In 32 bits system and 1024 bits size, in the worst case, We need 1024
for-loops to find 1
On 2013/4/9 10:16, Steven Rostedt wrote:
> On Tue, 2013-04-09 at 10:08 +0800, zhangwei(Jovi) wrote:
>> On 2013/4/9 4:49, Steven Rostedt wrote:
>>> From: "Steven Rostedt (Red Hat)"
>>>
>>> The function tracing control loop used by perf spits out a warning
>>> if the called function is not a
We're going to introduce support to read and write the memory
mapped timer registers in the next patch, so push the cp15
read/write functions one level deeper. This simplifies the next
patch and makes it clearer what's going on.
Cc: Mark Rutland
Cc: Marc Zyngier
Signed-off-by: Stephen Boyd
---
Add support for the memory mapped timers by filling in the
read/write functions and adding some parsing code. Note that we
only register one clocksource, preferring the cp15 based
clocksource over the mmio one.
To keep things simple we register one global clockevent. This
covers the case of UP
There isn't any reason why we don't pass the event here and we'll
need it in the near future for memory mapped arch timers anyway.
Cc: Mark Rutland
Cc: Marc Zyngier
Signed-off-by: Stephen Boyd
---
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Add a binding for the arm architected timer hardware's memory
mapped interface. The mmio timer hardware is made up of one base
frame and a collection of up to 8 timer frames, where each of the
8 timer frames can have either one or two views. A frame
typically maps to a privilege level
This patchset adds support for memory mapped architected timers. We
don't have any other global broadcast timer in our system, so we use the
mmio timer during low power modes. The first patch is the binding.
The next two patches lay some groundwork so that the last patch is simpler.
The final
From: Li Zefan
A couple controllers want to determine whether two cgroups are in
ancestor/descendant relationship. As it's more likely that the
descendant is the primary subject of interest and there are other
operations focusing on the descendants, let's ask is_descendent rather
than
perf_event is one of a couple remaining cgroup controllers with broken
hierarchy support. Converting it to support hierarchy is almost
trivial. The only thing necessary is to consider a task belonging to
a descendant cgroup as a match. IOW, if the cgroup of the currently
executing task
From: Li Zefan
Suppose we rmdir a cgroup and there're still css refs, this cgroup won't
be freed. Then we rmdir the parent cgroup, and the parent is freed
immediately due to css ref draining to 0. Now it would be a disaster if
the still-alive child cgroup tries to access its parent.
Make sure
perf_event cgroup controller is one of the remaining few with broken
hierarchy support. It turns out it's pretty easy to implement - the
only thing necessary is making perf_cgroup_match() return %true also
when the cgroup of the current task is a descendant of the event's
cgroup. This patchset
On Mon, Apr 08, 2013 at 05:36:42PM -0700, John Stultz wrote:
> On 04/07/2013 05:46 PM, Minchan Kim wrote:
> >Hello John,
> >
> >As you know, userland people wanted to handle vrange with mmaped
> >pointer rather than fd-based and see the SIGBUS so I thought more
> >about semantic of vrange and want
On Tue, 2013-04-09 at 10:08 +0800, zhangwei(Jovi) wrote:
> On 2013/4/9 4:49, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > The function tracing control loop used by perf spits out a warning
> > if the called function is not a control function. This is because
> > the control
On 2013/4/9 4:49, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> The function tracing control loop used by perf spits out a warning
> if the called function is not a control function. This is because
> the control function references a per cpu allocated data structure
> on struct
Hi will,
On 04/08/2013 06:55 PM, Will Deacon wrote:
> Given that we don't have NUMA support or memory-hotplug on arm64 yet, I'm
> not sure that this change makes much sense at the moment. early_pfn_to_nid
> will always return 0 and we only ever have one node.
>
> To be honest, I'm not sure what
Hi Yinghai,
On 04/09/2013 02:40 AM, Yinghai Lu wrote:
> On Mon, Apr 8, 2013 at 2:56 AM, Lin Feng wrote:
>> In hot add node(memory) case, vmemmap pages are always allocated from other
>> node,
>
> that is broken, and should be fixed.
> vmemmap should be on local node even for hot add node.
>
Hi Andrew,
On 04/09/2013 04:55 AM, Andrew Morton wrote:
> On Mon, 8 Apr 2013 11:40:11 -0700 Yinghai Lu wrote:
>
>> On Mon, Apr 8, 2013 at 2:56 AM, Lin Feng wrote:
>>> In hot add node(memory) case, vmemmap pages are always allocated from other
>>> node,
>>
>> that is broken, and should be
Currently, a write to /proc/pid/write will return the number of bytes
successfully written. If the actual string is greater than this, the
remainder of the string will normally be written.
This results in things such as
$ echo -n "abcdefghijklmnopqrs" > /proc/self/comm
to result in
On Tue, Apr 09, 2013 at 09:46:39AM +0800, Yijing Wang wrote:
> CONFIG_HOTPLUG is going away as an option, cleanup CONFIG_HOTPLUG
> ifdefs in i2c files.
>
> Signed-off-by: Yijing Wang
> Cc: Greg Kroah-Hartman
> Cc: Bill Pemberton
Acked-by: Greg Kroah-Hartman
--
To unsubscribe from this list:
On 04/08/2013 03:18 PM, KOSAKI Motohiro wrote:
(4/8/13 3:49 PM), Cody P Schafer wrote:>
If this turns out to be an issue, schedule_on_each_cpu() could be an
alternative.
no way. schedule_on_each_cpu() is more problematic and it should be removed
in the future.
schedule_on_each_cpu() can only
On 2013年04月08日 21:45, Rusty Russell wrote:
>> >
>> > and for this patch, is it suitable to send patch v2 ?
> Yes, that's fine.
>
thanks, I will send patch v2 (the subject need delete "strncpy issue")
>>> >> However, kallsyms_lookup also calls kallsyms_expand_symbol, which
>>> >> doesn't stop
On 8 April 2013 17:37, Theodore Ts'o wrote:
> There shouldn't be any crap; just a an error message indicating that
> "the file system has features which this implementation doesn't
> understand". At least, if the implementation was competently
> coded (ext2/3/4 has feature bitmasks that
CONFIG_HOTPLUG is going away as an option, cleanup CONFIG_HOTPLUG
ifdefs in i2c files.
Signed-off-by: Yijing Wang
Cc: Greg Kroah-Hartman
Cc: Bill Pemberton
---
drivers/i2c/i2c-core.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/drivers/i2c/i2c-core.c
On 2013年04月08日 23:31, tip-bot for Chen Gang wrote:
> Commit-ID: 75761cc15877c155b3849b4e0e0cb3f897faf471
> Gitweb: http://git.kernel.org/tip/75761cc15877c155b3849b4e0e0cb3f897faf471
> Author: Chen Gang
> AuthorDate: Mon, 8 Apr 2013 12:12:39 +0800
> Committer: Ingo Molnar
> CommitDate:
On Tue, Apr 09, 2013 at 10:27:19AM +0900, Minchan Kim wrote:
> Hi Dan,
>
> On Mon, Apr 08, 2013 at 09:32:38AM -0700, Dan Magenheimer wrote:
> > > From: Minchan Kim [mailto:minc...@kernel.org]
> > > Sent: Monday, April 08, 2013 12:01 AM
> > > Subject: [PATCH] mm: remove compressed copy from zram
Hi Ingo,
Any chance for this patchset and the other one to be queued for 3.10?
Both of them has been acked by Peter.
On 2013/3/29 18:36, Peter Zijlstra wrote:
> On Fri, 2013-03-29 at 14:43 +0800, Li Zefan wrote:
>> cpuacct is the only user of cgroup_subsys.active flag.
>>
>> The flag is needed
On 2013/4/8 22:25, Michal Hocko wrote:
> On Mon 08-04-13 14:36:52, Li Zefan wrote:
> [...]
>> @@ -5188,12 +5154,28 @@ static int mem_cgroup_dangling_read(struct cgroup
>> *cont, struct cftype *cft,
>> struct seq_file *m)
>> {
>> struct mem_cgroup *memcg;
Hi Dan,
On Mon, Apr 08, 2013 at 09:32:38AM -0700, Dan Magenheimer wrote:
> > From: Minchan Kim [mailto:minc...@kernel.org]
> > Sent: Monday, April 08, 2013 12:01 AM
> > Subject: [PATCH] mm: remove compressed copy from zram in-memory
>
> (patch removed)
>
> > Fragment ratio is almost same but
On 2013年04月09日 04:45, Lars Ellenberg wrote:
> On Wed, Apr 03, 2013 at 04:00:31PM +0800, Chen Gang wrote:
>> > Hello maintainers:
>> >
>> > when you have time, please help to check this patch whether is OK.
>> >
>> > thanks.
> Thanks.
>
> It has already been queued in:
>
This patch fix the below compilation warning:
linux/drivers/net/ethernet/broadcom/tg3.c: In function
'tg3_hwclock_to_timestamp':
linux/drivers/net/ethernet/broadcom/tg3.c:5686: warning: integer constant is
too large for 'long' type
Signed-off-by: Wang YanQing
---
In shrink_(in)active_list(), we can fail to put into lru, and these pages
are reclaimed accidentally. Currently, these pages are not counted
for sc->nr_reclaimed, but with this information, we can stop to reclaim
earlier, so can reduce overhead of reclaim.
Signed-off-by: Joonsoo Kim
diff --git
Currently, freed pages via rcu is not counted for reclaimed_slab, because
it is freed in rcu context, not current task context. But, this free is
initiated by this task, so counting this into this task's reclaimed_slab
is meaningful to decide whether we continue reclaim, or not.
So change code to
Currently, freed pages via rcu is not counted for reclaimed_slab, because
it is freed in rcu context, not current task context. But, this free is
initiated by this task, so counting this into this task's reclaimed_slab
is meaningful to decide whether we continue reclaim, or not.
So change code to
From: Jason Hrycay
Move the f2fs_balance_fs out of the truncate_hole function and only
perform that in punch_hole use case. The commit:
ed60b1644e7f7e5dd67d21caf7e4425dff05dad0
intended to do this but moved it into truncate_hole to cover more
cases. However, a deadlock scenario is possible
On 04/08/2013 06:03 PM, Sebastian Andrzej Siewior wrote:
> On 04/05/2013 09:21 AM, Lai Jiangshan wrote:
>> Hi, Sebastian
>
> Hi Lai,
>
>> I don't want to expose __SRCU_STRUCT_INIT(),
>> due to it has strong coupling with the percpu array.
>>
>> I hope other structure which uses SRCU should use
2013/4/9, Steven Rostedt :
> On Sat, 2013-04-06 at 14:45 +0900, Namjae Jeon wrote:
>> From: Namjae Jeon
>>
>> Add tracepoints in f2fs filesystem for tracing the filesystem
>> operations for information/debugging purpose if needed. All the
>> tracepoints are clubbed with respect to
Hi Andrew,
On Mon, Apr 08, 2013 at 02:17:10PM -0700, Andrew Morton wrote:
> On Mon, 8 Apr 2013 15:01:02 +0900 Minchan Kim wrote:
>
> > Swap subsystem does lazy swap slot free with expecting the page
> > would be swapped out again so we can avoid unnecessary write.
>
> Is that correct? How
On Mon, Apr 08, 2013 at 02:34:38PM -0700, Kees Cook wrote:
> On Mon, Apr 1, 2013 at 6:05 PM, Josh Boyer wrote:
> > - Original Message -
> >> From: "Kees Cook"
> >> To: "Josh Boyer"
> >> Cc: "Andrew Morton" , "Eric Paris"
> >> , "Linus Torvalds"
> >> , "Christian Kujau"
> >> , "#
On 04/08/2013 11:27 AM, Eduardo Valentin wrote:
Thanks for your patch. But as mentioned by Greg, this file does not
exist anymore, it has been renamed. Check latest linux-next.
Besides, the issue you are fixing has been already removed. Also check
latest linux-next and you will see the driver
On Mon, Apr 08, 2013 at 04:12:07PM -0700, Adrian Chadd wrote:
> I'm a FreeBSD user. I know what it's like to have an alternate, out of
> linux implementation of ext2/3 that doesn't implement all of the
> features.
>
> I also know what kinds of crap happens when you try mounting a more
> recent
On 04/07/2013 05:46 PM, Minchan Kim wrote:
Hello John,
As you know, userland people wanted to handle vrange with mmaped
pointer rather than fd-based and see the SIGBUS so I thought more
about semantic of vrange and want to make it very clear and easy.
So I suggest below semantic(Of course, it's
On Sat, 2013-04-06 at 10:10 +0200, Thomas Gleixner wrote:
> The sched_clock_remote() implementation has the following inatomicity
> problem on 32bit systems when accessing the remote scd->clock, which
> is a 64bit value.
>
> CPU0 CPU1
>
> sched_clock_local()
On Sat, 2013-04-06 at 14:45 +0900, Namjae Jeon wrote:
> From: Namjae Jeon
>
> Add tracepoints in f2fs filesystem for tracing the filesystem
> operations for information/debugging purpose if needed. All the
> tracepoints are clubbed with respect to functionalities.
>
> Change Log:
> v3:
ping ...
在 2013-03-04一的 09:21 +0800，li guang写道：
> Hi, Thomas, Peter, Ingo
>
> can you help to merge these 4 patches?
> or do you have any other comments?
>
>
> 在 2013-02-25一的 10:38 +0800，liguang写道：
> > just do some trivial changes to make acpi's numa info
> > operation more cleaner.
> >
> >
When CONFIG_XHCI_HCD_DEBUGGING is activated, the XHCI driver can dump
device and input contexts to the console. The endpoint contexts in that
dump are labeled "Endpoint N Context", where N is the XHCI endpoint
index (DCI - 1). This can be very confusing, especially for people who
are not that
On Tue, Apr 09, 2013 at 02:41:32AM +0300, Tomas Winkler wrote:
> v5 -> v6
> 1. include/linux/uapi/mei/nfc.h - provides API also for pure
> user space implementation as found under Android.
> 2. Removed INTEL_MEI_BUS_NFC Kconfig option.
> The NFC info client is disconnected as soon as we
When selecting a target cooling state in get_target_state(), make sure
that the state is at least as high as the minimum when the temperature
is rising and at least as low as the maximum when the temperature is
falling. Previously the cooling level would only be incremented or
decremented by one
1 - 100 of 1828 matches
Mail list logo
