identical touchscreens.
Signed-off-by: Vladimir Shebordaev <[EMAIL PROTECTED]>
---
drivers/input/touchscreen/usbtouchscreen.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/input/touchscreen/usbtouchscreen.c
b/drivers/input/touchscreen/usbtouchscreen.c
index e
From: Vladimir Shebordaev <[EMAIL PROTECTED]>
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g.
From: Vladimir Shebordaev <[EMAIL PROTECTED]>
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g.
Hi!
we have an NFS server (windows-based), and mount a directory from this
server on a linux box; there is some bug appearing sometimes, namely
some of the directory entries are reported twice:
$ ls | wc
59685968 41776
$ ls | uniq | wc
59645964 41748
$ ls | uniq -d
112920
112921
"TM" == Trond Myklebust writes:
>> i.e. the current directory contains sub-directory 112920 twice,
>> sub-directory 112921 twice, etc. - and the inode numbers are the
>> same.
TM> That can happen if the NFS server doesn't send unique cookies.
i have 2 questions:
1) how to debug this, to con
Hi all,
I'm looking for a way to implement polling for sysfs attribute files.
There seem to be sysfs_poll API but I have no idea how to use it
correctly.
Any hint, example of usage or comment wold be deeply appreciated.
--
Sincerely,
Vladimir "Farcaller" Pouzanov
-
To unsubs
so I don't know where
should I start looking for a bug.
F3T is based on Thrion64 X2 CPU (I'm running it in x86 mode with SMP and
PREEMPT).
Sincerely,
Vladimir "Farcaller" Pouzanov
http://hackndev.com
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
alue to see if we can break out.
>
> Does this actually change anything? Maybe I am missing something but
> try_to_free_mem_cgroup_pages which is the main entry for the memcg
> reclaim doesn't set reclaim_state. I don't remember why... Vladimir?
We don't set reclaim_s
On Thu, Jul 21, 2016 at 08:41:44AM -0400, Johannes Weiner wrote:
> On Mon, Jun 27, 2016 at 07:39:54PM +0300, Vladimir Davydov wrote:
> > When selecting an oom victim, we use the same heuristic for both memory
> > cgroup and global oom. The only difference is the scope of tasks to
rain operation
> will put references of in-use pages, thus causing the imbalance.
>
> Disable IRQs during all per-cpu charge cache operations.
>
> Fixes: f7e1cb6ec51b ("mm: memcontrol: account socket memory in unified
> hierarchy memory controller")
> Cc: # 4.5+
> Signed-off-by: Johannes Weiner
Acked-by: Vladimir Davydov
s are destroyed later on.
>
> Fixes: bd1060a1d671 ("sock, cgroup: add sock->sk_cgroup")
> Cc: # 4.5+
> Signed-off-by: Johannes Weiner
Reviewed-by: Vladimir Davydov
Hi,
On 09/20/2016 03:55 PM, Shawn Guo wrote:
On Sun, Sep 18, 2016 at 01:24:42PM +0200, Linus Walleij wrote:
On Sun, Sep 18, 2016 at 2:59 AM, Guenter Roeck wrote:
On 09/17/2016 05:08 PM, Shawn Guo wrote:
Hi Guenter,
On Thu, Sep 15, 2016 at 04:35:04PM +0300, Vladimir Zapolskiy wrote:
The
map)) {
> pr_err("failed to regmap system control block: %ld\n",
> PTR_ERR(clk_regmap));
> + iounmap(base);
> return;
> }
>
>
Acked-by: Vladimir Zapolskiy
Thank you for the patch.
--
With best wishes,
Vladimir
; Since frv has THREAD_SIZE < PAGE_SIZE, we need to track kernel stack
> allocations in a unit that divides both THREAD_SIZE and PAGE_SIZE on
> all architectures. Keep it simple and use KiB.
>
> Cc: Vladimir Davydov
> Cc: Johannes Weiner
> Cc: Michal Hocko
> Cc: linux...@kva
12580e4b54ba8 ("mm: memcontrol: report kernel stack usage in cgroup2
> memory.stat")
> Cc: Vladimir Davydov
> Cc: Johannes Weiner
> Cc: Michal Hocko
> Cc: linux...@kvack.org
> Signed-off-by: Andy Lutomirski
Reviewed-by: Vladimir Davydov
This patch is going to have
65K cgroups it will take the reclaimer a substantial amount of time
to iterate over all of them, which might result in latency spikes.
Probably, to avoid that, we could move pages from a dead cgroup's lru to
its parent's one on offline while still leaving dead cgroups pinned,
like we do i
;0038fdaa>] aio_migratepage+0x16a/0x1e8)
> ([<00310568>] move_to_new_page+0xb0/0x260)
> ([<003111b4>] migrate_pages+0x8f4/0x9f0)
> ([<002c507c>] compact_zone+0x4dc/0xdc8)
> ([<002c5e22>] kcompactd_do_work+0x1aa/0x358)
> ([<002c608a>] kcompactd+0xba/0x2c8)
> ([<0016b09a>] kthread+0x10a/0x110)
> ([<0095315a>] kernel_thread_starter+0x6/0xc)
> ([<00953154>] kernel_thread_starter+0x0/0xc)
> INFO: lockdep is turned off.
>
> Signed-off-by: Tejun Heo
> Reported-by: Christian Borntraeger
> Link: http://lkml.kernel.org/g/5767cfe5.7080...@de.ibm.com
Reviewed-by: Vladimir Davydov
s on
.gpio_disable_free call for non-Vybrid platforms?
--
With best wishes,
Vladimir
Hi Stefan,
On 09/27/2016 07:37 PM, Stefan Agner wrote:
On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
Hi Stefan,
On 09/27/2016 03:26 AM, Stefan Agner wrote:
If a GPIO gets freed after selecting a new pinctrl configuration
the driver should not change pinctrl anymore. Otherwise this will
On 09/27/2016 10:34 PM, Stefan Agner wrote:
On 2016-09-27 11:17, Vladimir Zapolskiy wrote:
Hi Stefan,
On 09/27/2016 07:37 PM, Stefan Agner wrote:
On 2016-09-27 05:12, Vladimir Zapolskiy wrote:
Hi Stefan,
On 09/27/2016 03:26 AM, Stefan Agner wrote:
If a GPIO gets freed after selecting a new
never invoked on global reclaim. Fix that.
Fixes: d71df22b55099 ("mm, vmscan: begin reclaiming pages on a per-node basis")
Signed-off-by: Vladimir Davydov
---
mm/vmscan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 650d26832569..37
many
small jobs")
Signed-off-by: Vladimir Davydov
---
mm/memcontrol.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 5fe285f27ea7..58c229071fb1 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -4030,9 +
")
Signed-off-by: Vladimir Davydov
---
mm/memcontrol.c | 27 +--
1 file changed, 21 insertions(+), 6 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index b5804e4e6324..5fe285f27ea7 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -4035,6 +4035,13 @@ static v
On Mon, Aug 01, 2016 at 12:00:21PM +0200, Michal Hocko wrote:
...
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index c265212bec8c..eb7e39c2d948 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2543,6 +2543,11 @@ static int mem_cgroup_resize_memsw_limit(struct
> mem_cgroup *memcg,
radix tree nodes if it was explicitly requested by passing
__GFP_ACCOUNT to INIT_RADIX_TREE. Currently, we only want to account
page cache entries, so mark mapping->page_tree so.
Signed-off-by: Vladimir Davydov
---
fs/inode.c | 2 +-
lib/radix-tree.c | 14 ++
2 files cha
l oom heuristic related code
private to oom_kill.c and make oom_kill.c use exported memcg functions
when it's really necessary (like in case of iterating over memcg tasks).
Signed-off-by: Vladimir Davydov
Acked-by: Johannes Weiner
---
Changes in v3:
- rebase on top of v4.7-mmotm-2016-07-28-16-33
.
Guenter, thank you for the early report.
--
With best wishes,
Vladimir
this in isolation
with your Reported-by.
please revert the revert :)
--
With best wishes,
Vladimir
Hi Guenter,
On 09/14/2016 06:20 AM, Guenter Roeck wrote:
Hi Vladimir,
your commit e188cbf7564f ("gpio: mxc: shift gpio_mxc_init() to subsys_initcall
level")
in -next causes the following crash when running the 'kzm' target (and most
likely
the real thing) with qemu.
[
Hi Linus,
On 09/15/2016 04:18 PM, Vladimir Zapolskiy wrote:
Hi Linus,
On 09/15/2016 03:19 PM, Linus Walleij wrote:
On Wed, Sep 14, 2016 at 4:33 PM, Guenter Roeck wrote:
On 09/14/2016 12:19 AM, Linus Walleij wrote:
On Wed, Sep 14, 2016 at 5:20 AM, Guenter Roeck wrote:
So, in other words
vdavydov@{parallels,virtuozzo}.com will bounce from now on.
Signed-off-by: Vladimir Davydov
---
.mailmap| 2 ++
MAINTAINERS | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/.mailmap b/.mailmap
index b18912c5121e..de22daefd9da 100644
--- a/.mailmap
+++ b/.mailmap
h_spin_unlock() code only uses an STLR
> without an explicit SEV (like we have on AArch32). An event is
> automatically generated when the exclusive monitor is cleared by STLR.
> But without setting it with a load exclusive in arch_spin_lock() (even
> though it does not acquire the lock), there won't be anything to clear,
> hence no event to be generated. In this case, the WFE would wait
> indefinitely.
>
Maybe worth to add this as a comment, no?
Cheers
Vladimir
On Wed, Aug 31, 2016 at 07:26:43AM -0700, Greg wrote:
> On Wed, 2016-08-31 at 15:01 +0300, Vladimir Davydov wrote:
> > vdavydov@{parallels,virtuozzo}.com will bounce from now on.
> >
> > Signed-off-by: Vladimir Davydov
>
> Shouldn't MAINTAINERS be in the subject
Hi
On 01/09/16 16:06, Laurentiu Tudor wrote:
> Mention that arm64 also has kasan support.
It seems that similar patch was already sent before [1]
[1] https://lkml.org/lkml/2016/8/16/566
Vladimir
>
> Signed-off-by: Laurentiu Tudor
> ---
> Documentation/kasan.txt | 2 +-
>
llows to avoid overlappings on SRAM areas,
and still other drivers may serve as consumers of partitions on SRAM.
Please add me to Cc list when you send the next version of the driver.
With best wishes,
Vladimir
thanks
-john
Cc: Andy Yan
Cc: Rob Herring
Cc: Arnd Bergmann
Cc: Thierry Reding
Cc:
Hi Rob,
On 08/06/2016 01:37 AM, Rob Herring wrote:
On Fri, Aug 5, 2016 at 7:46 AM, Vladimir Zapolskiy
wrote:
Hi John,
On 08/04/2016 02:05 AM, John Stultz wrote:
Now that Andy's reboot reason core driver has landed, I wanted
to resubmit a reworked version of my SRAM based reboot r
should only be set for pages that are
actually accounted to a non-root kmemcg and hence pin memcg_kmem_enabled
static key. I'll fix that.
Thanks,
Vladimir
uot;)
Reported-by: Eric Dumazet
Signed-off-by: Vladimir Davydov
Cc: [4.7+]
---
fs/pipe.c | 4 +---
mm/memcontrol.c | 14 --
mm/page_alloc.c | 14 +-
3 files changed, 18 insertions(+), 14 deletions(-)
diff --git a/fs/pipe.c b/fs/pipe.c
index 4b32928f5426..4ebe6b2e5217
l: fix swap counter leak on swapout from
> offline cgroup")
Acked-by: Vladimir Davydov
+Christoph since he is trying to consolidate work in this area [1].
Christoph, any chance you can look into patches touching
dma-{coherent,noop}.c?
[1] https://patchwork.ozlabs.org/patch/778254/
Thanks!
Vladimir
On 15/06/17 08:25, Vladimir Murzin wrote:
> Greg?
>
> On 08/06/17 17:25
x10
>
> Fix this lockup by reducing the number of entries to be shrinked
> from the lru list to 1024 at once. Also, add cond_resched() before
> processing the lru list again.
>
> Link: http://marc.info/?t=14972286491&r=1&w=2
> Fix-suggested-by: Jan kara
>
On 20/06/17 14:23, Christoph Hellwig wrote:
> On Wed, May 24, 2017 at 11:24:27AM +0100, Vladimir Murzin wrote:
>> This patch adds a simple implementation of mmap to dma_noop_ops.
>
> Currently we use dma_common_mmap as the generic fallback if a dma_ops
> instance doesn't
.
Will do.
>
> Otherwise this looks fine to me.
>
Thanks
Vladimir
dev_addr, rmem->size,
> DMA_MEMORY_MAP | DMA_MEMORY_EXCLUSIVE,
> &mem)) {
> pr_err("Reserved memory: failed to init DMA memory pool at %pa,
> size %ld MiB\n",
>
Robin has already commented on this - dma_pfn_offset may vary across devices
and reserved memory region may be shared between them.
Cheers
Vladimir
On 20/06/17 14:49, Christoph Hellwig wrote:
> On Wed, May 24, 2017 at 11:24:29AM +0100, Vladimir Murzin wrote:
>> This patch introduces default coherent DMA pool similar to default CMA
>> area concept. To keep other users safe code kept under CONFIG_ARM.
>
> I don't se
NABLED(CONFIG_MMU) ? &arm_dma_ops : &dma_noop_ops;
What toolchain are you using?
Cheers
Vladimir
>
>
> On Mon, Oct 16, 2017 at 2:28 PM, Randy Dunlap wrote:
>> On 10/15/17 20:29, Randy Dunlap wrote:
>>> On 10/15/17 20:27, Randy Dunlap wrote:
&g
a
> reasonable compromise.
.. or you can just keep shadow in page extension. It was suggested back in
2015 [1], but seems that lack of stack instrumentation was "no-way"...
[1] https://lkml.org/lkml/2015/8/24/573
Cheers
Vladimir
On 30/05/17 09:15, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 9:58 AM, Vladimir Murzin
> wrote:
>> On 29/05/17 16:29, Dmitry Vyukov wrote:
>>> I have an alternative proposal. It should be conceptually simpler and
>>> also less arch-dependent. But I don't kno
On 30/05/17 09:31, Vladimir Murzin wrote:
> [This sender failed our fraud detection checks and may not be who they appear
> to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]
>
> On 30/05/17 09:15, Dmitry Vyukov wrote:
>> On Tue, May 30, 2017 at 9:58 AM, Vladimi
On 30/05/17 09:49, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 10:40 AM, Vladimir Murzin
> wrote:
>> On 30/05/17 09:31, Vladimir Murzin wrote:
>>> [This sender failed our fraud detection checks and may not be who they
>>> appear to be. Learn about spoofing at ht
On 30/05/17 10:26, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 11:08 AM, Vladimir Murzin
> wrote:
>>> wrote:
>>>> On 30/05/17 09:31, Vladimir Murzin wrote:
>>>>> [This sender failed our fraud detection checks and may not be who they
>>>>
On 30/05/17 10:45, Dmitry Vyukov wrote:
> On Tue, May 30, 2017 at 11:39 AM, Vladimir Murzin
> wrote:
>>
>> On 30/05/17 10:26, Dmitry Vyukov wrote:
>>> On Tue, May 30, 2017 at 11:08 AM, Vladimir Murzin
>>> wrote:
>>>>> wrote:
>>>>&g
; Fixes: 877ec119dbbf ("ARM: 8706/1: NOMMU: Move out MPU setup in separate
> module")
> Signed-off-by: Arnd Bergmann
> ---
> Vladimir, if this looks good to you, can you forward it to Russell's
> patch tracker, or otherwise suggest a different fix?
Accepted as patch 8719/1.
On 02/11/17 13:07, Russell King - ARM Linux wrote:
> On Thu, Nov 02, 2017 at 12:25:47PM +0000, Vladimir Murzin wrote:
>> On 02/11/17 09:21, Arnd Bergmann wrote:
>>> The reworked MPU code produces a new warning in some configurations,
>>> presumably starting with the c
Hi Kamil,
On 10/24/2017 01:19 PM, Kamil Konieczny wrote:
> Hi Vladimir,
>
> Thank you for review.
>
> On 22.10.2017 12:18, Vladimir Zapolskiy wrote:
>> Hi Kamil,
>>
>> On 10/17/2017 02:28 PM, Kamil Konieczny wrote:
>>> change spaces into tabs in
Hi Kamil,
I'll just answer to your question, all the comments from you are accepted,
please send a new version with the minor fixes, hopefully the change will
be included into v4.15-rc.
On 10/24/2017 02:27 PM, Kamil Konieczny wrote:
> Hi Vladimir,
>
> Thank you for review, I wil
; Signed-off-by: Kamil Konieczny
> ---
I won't linger this time :)
Please feel free to add
Acked-by: Vladimir Zapolskiy
--
With best wishes,
Vladimir
on);
> +
> + vde->miscdev.minor = MISC_DYNAMIC_MINOR;
> + vde->miscdev.name = "tegra_vde";
> + vde->miscdev.fops = &tegra_vde_fops;
> + vde->miscdev.parent = dev;
> +
> + err = misc_register(&vde->miscdev);
> + if (err) {
> + dev_err(dev, "Failed to register misc device: %d\n", err);
> + goto err_gen_free;
> + }
> +
> + pm_runtime_enable(dev);
> + pm_runtime_use_autosuspend(dev);
> + pm_runtime_set_autosuspend_delay(dev, 300);
> +
> + if (!pm_runtime_enabled(dev)) {
> + err = tegra_vde_runtime_resume(dev);
> + if (err)
> + goto err_misc_unreg;
> + }
> +
> + return 0;
> +
> +err_misc_unreg:
> + misc_deregister(&vde->miscdev);
> +
> +err_gen_free:
> + gen_pool_free(vde->iram_pool,
> + (unsigned long)vde->iram, 0x3FC00);
See a comment above.
> +
> + return err;
> +}
> +
> +static int tegra_vde_remove(struct platform_device *pdev)
> +{
> + struct tegra_vde *vde = platform_get_drvdata(pdev);
> + struct device *dev = &pdev->dev;
> + int err;
> +
> + if (!pm_runtime_enabled(dev)) {
> + err = tegra_vde_runtime_suspend(dev);
> + if (err)
> + return err;
> + }
> +
> + pm_runtime_dont_use_autosuspend(dev);
> + pm_runtime_disable(dev);
> +
> + misc_deregister(&vde->miscdev);
> +
> + gen_pool_free(vde->iram_pool,
> + (unsigned long)vde->iram, 0x3FC00);
See a comment above.
> +
> + return 0;
> +}
> +
[snip]
> +
> +MODULE_DESCRIPTION("NVIDIA Tegra20 Video Decoder driver");
> +MODULE_AUTHOR("Dmitry Osipenko");
Please add your email here, then if you are not a maintainer (and by
the way please consider to add your name to the MAINTAINERS file),
you'll get a higher chance to receive updates in the future.
> +MODULE_LICENSE("GPL");
>
--
With best wishes,
Vladimir
Hi Dmitry,
On 10/20/2017 12:34 AM, Dmitry Osipenko wrote:
> From: Vladimir Zapolskiy
>
> All Tegra SoCs contain 256KiB IRAM, which is used to store CPU resume code
> and by hardware engines like a video decoder.
>
> Signed-off-by: Vladimir Zapolskiy
Please add also your o
eo frame controls */>;
> + reg-names = "sxe", "bsev", "mbe", "ppe", "mce",
> + "tfe", "ppb", "vdma", "frameid";
> + iram = <&vde_pool>; /* IRAM region */
> + interrupts = , /* Sync token interrupt
> */
> + , /* BSE-V interrupt */
> + ; /* SXE interrupt */
> + interrupt-names = "sync-token", "bsev", "sxe";
> + clocks = <&tegra_car TEGRA20_CLK_VDE>;
> + resets = <&tegra_car 61>;
> +};
>
--
With best wishes,
Vladimir
on/devicetree/bindings/clock/clock-bindings.txt
about how to assign initial clock rates, in general 'clock-frequency'
property is a property of clock consumers with two exceptions of simple
clock sources, namely it is used in fixed clock and PWM clock bindings.
--
With best wishes,
Vladimir
Hello,
This adds the folowing:
- Holt threshold detector driver for HI-8435 chip
- Document HI-8435 DT bindings
PDF file can be found here:
http://www.holtic.com/products/3081-hi-8435.aspx
Vladimir Barinov (2):
[1/2] iio: adc: hi8435: Holt HI-8435 threshold detector
[2/2] dt: Document Holt HI
Add Holt threshold detector driver for HI-8435 chip
Signed-off-by: Vladimir Barinov
---
Changes in version 2:
- Added file sysfs-bus-iio-adc-hi8435
- Changed naming from "discrete ADC" to "threshold detector"
- Replaced swab16p/swab32p with be16_to_cpup/be32_to_cpup
- Mad
These bindings can be used to register Holt HI-8435 threshold detector
Signed-off-by: Vladimir Barinov
---
Changes in version 2:
- renamed file name hi-843x.txt to hi8435.txt
- removed hi-8436,hi-8436,hi-8437
- removed holt,debounce-soft field
- renamed holt,debounc-soft-delay to holt,debounce
used
without it is fallback_alloc(), which, in contrast to other
cache_grow() users, preallocates a page and passes it to cache_grow()
so that the latter does not need to invoke kmem_getpages() by itself.
Reported-by: Tejun Heo
Signed-off-by: Vladimir Davydov
orwarding it to memcg_charge_slab()
if the context allows.
Reported-by: Tejun Heo
Signed-off-by: Vladimir Davydov
---
mm/slub.c | 24 +++-
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/mm/slub.c b/mm/slub.c
index e180f8dcd06d..416a332277cb 100644
--- a/mm/slub.c
pages, memcg reclaim will
not get invoked on kmem allocations, which will lead to uncontrollable
growth of memory usage no matter what memory.high is set to.
This patch set attempts to fix this issue. For more details please see
comments to individual patches.
Thanks,
Vladimir Davydov (2):
mm
On Mon, Aug 31, 2015 at 03:24:15PM +0200, Michal Hocko wrote:
> On Sun 30-08-15 22:02:16, Vladimir Davydov wrote:
> > Tejun reported that sometimes memcg/memory.high threshold seems to be
> > silently ignored if kmem accounting is enabled:
> >
> > http://www.spinics.
) any time with any flags they want and
it won't be accounted to memcg, because kmem is accounted at slab/slub
layer, not in buddy.
Thanks,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mor
On Mon, Aug 31, 2015 at 10:39:39AM -0400, Tejun Heo wrote:
> On Mon, Aug 31, 2015 at 05:30:08PM +0300, Vladimir Davydov wrote:
> > slab/slub can issue alloc_pages() any time with any flags they want and
> > it won't be accounted to memcg, because kmem is accounted at slab/sl
On Mon, Aug 31, 2015 at 10:46:04AM -0400, Tejun Heo wrote:
> Hello, Vladimir.
>
> On Mon, Aug 31, 2015 at 05:20:49PM +0300, Vladimir Davydov wrote:
> ...
> > That being said, this is the fix at the right layer.
>
> While this *might* be a necessary workaround for the har
On Mon, Aug 31, 2015 at 11:47:56AM -0400, Tejun Heo wrote:
> On Mon, Aug 31, 2015 at 06:18:14PM +0300, Vladimir Davydov wrote:
> > We have to be cautious about placing memcg_charge in slab/slub. To
> > understand why, consider SLAB case, which first tries to allocate from
>
On Mon, Aug 31, 2015 at 01:03:09PM -0400, Tejun Heo wrote:
> On Mon, Aug 31, 2015 at 07:51:32PM +0300, Vladimir Davydov wrote:
> ...
> > If we want to allow slab/slub implementation to invoke try_charge
> > wherever it wants, we need to introduce an asynchronous thread doing
On Mon, Aug 31, 2015 at 03:22:22PM -0500, Christoph Lameter wrote:
> On Mon, 31 Aug 2015, Vladimir Davydov wrote:
>
> > I totally agree that we should strive to make a kmem user feel roughly
> > the same in memcg as if it were running on a host with equal amount of
> > RA
On Tue, Sep 01, 2015 at 02:36:12PM +0200, Michal Hocko wrote:
> On Mon 31-08-15 17:20:49, Vladimir Davydov wrote:
> > On Mon, Aug 31, 2015 at 03:24:15PM +0200, Michal Hocko wrote:
> > > On Sun 30-08-15 22:02:16, Vladimir Davydov wrote:
> >
> > > > Tejun repor
On Tue, Sep 01, 2015 at 05:01:20PM +0200, Michal Hocko wrote:
> On Tue 01-09-15 16:40:03, Vladimir Davydov wrote:
> > On Tue, Sep 01, 2015 at 02:36:12PM +0200, Michal Hocko wrote:
> > > On Mon 31-08-15 17:20:49, Vladimir Davydov wrote:
> {...}
> > > > 1. SLAB. S
t;> could be exporting the PWM with this ID. If I remember correctly this
>>>> was one of the reasons why the offending commit was merged in the first
>>>> place.
>>>
>>> Just for the record, when I proposed this fix to Nicolas, I clearly
>>&
On 09/09/15 04:59, Wang Long wrote:
> The current KASAN code can find the following out-of-bounds
Should it be "cannot"?
Vladimir
> bugs:
> char *ptr;
> ptr = kmalloc(8, GFP_KERNEL);
> memset(ptr+7, 0, 2);
>
> the cause of the problem
" moveq %1, %2\n" \
>>> " movne %0, %4\n" \
>>>
>>> so that we're not loading into %1 (an in-out non-temporary) but rather
>>> loading it into a temporary - an
On 15/10/15 14:02, Will Deacon wrote:
> On Thu, Oct 15, 2015 at 10:17:47AM +0100, Vladimir Murzin wrote:
>> We might need the same change for arm64 counterpart (see
>> arch/arm64/kernel/armv8_deprecated.c).
>
> Something like below?
Looks good. Should these two go to stable?
On 15/10/15 14:25, Vladimir Murzin wrote:
> On 15/10/15 14:02, Will Deacon wrote:
>> On Thu, Oct 15, 2015 at 10:17:47AM +0100, Vladimir Murzin wrote:
>>> We might need the same change for arm64 counterpart (see
>>> arch/arm64/kernel/armv8_deprecated.c).
>>
>>
On Fri, Oct 16, 2015 at 04:17:26PM +0300, Kirill A. Shutemov wrote:
> On Mon, Oct 05, 2015 at 01:21:43AM +0300, Vladimir Davydov wrote:
> > Before the previous patch, __mem_cgroup_from_kmem had to handle two
> > types of kmem - slab pages and pages allocated with alloc_kmem_pages -
On Fri, Oct 16, 2015 at 03:12:23PM -0700, Hugh Dickins wrote:
...
> Are you expecting to use mem_cgroup_from_kmem() from other places
> in future? Seems possible; but at present it's called from only
Not in the near future. At least, currently I can't think of any other
use for it except list_lru
On Fri, Oct 16, 2015 at 05:19:32PM -0700, Johannes Weiner wrote:
...
> I think it'd be better to have an outer function than a magic
> parameter for the memcg lookup. Could we fold this in there?
Yeah, that looks neater. Thanks!
Andrew, could you please fold this one too?
>
> ---
>
> Signed-of
o
what we have system-wide. In other words, Glauber's work makes sense to
me. You might want to point me at my RFC patch where I proposed to
revert it (https://lkml.org/lkml/2014/9/12/401). Well, I've changed my
mind since then. Now I think I was mistaken, luckily I was stopped.
However,
U, now we won't shrink the window on hitting the limit, i.e. this
patch subtly changes the behavior of the existing knobs, potentially
breaking them.
Thanks,
Vladimir
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
nt with the existing
behavior. I agree that we need to charge socker buffers to ->memory, but
IMO we should do that per each skb page, using memcg_kmem_charge_kmem
somewhere in alloc_skb_with_frags invoking the reclaimer just as we do
for kmalloc, while tcp window size control should stay aside.
staken, but AFAIU this patch subtly changes the behavior of
vmpressure visible from the userspace: w/o this patch a userspace
process will only receive a notification for a memory cgroup only if
*this* memory cgroup calls reclaimer; with this patch userspace
notification will be issued even if rec
ot_mem_cgroup)
> + memcg->socket_pressure = jiffies + HZ;
Why 1 second?
Thanks,
Vladimir
> + }
> +
> do {
> - if (vmpressure_event(vmpr, scanned, reclaimed))
> + if (vmpressure_event(vmpr, level))
>
ng Johannes to Cc (I noticed that I accidentally left him
out), because this discussion seems to be fundamental and may affect
our further steps dramatically.
]
On Tue, Sep 01, 2015 at 08:38:50PM +0200, Michal Hocko wrote:
> On Tue 01-09-15 19:55:54, Vladimir Davydov wrote:
> > On Tue, Sep
Hi Lars,
On 31.08.2015 17:57, Lars-Peter Clausen wrote:
On 08/17/2015 02:45 PM, Vladimir Barinov wrote:
Hello Daniel,
I've verified that your hrtimer trigger works.
I have minor suggestions.
Will not it be useful to have ability to stop/start hrtimer polling
not only during attach/d
On Wed, Sep 02, 2015 at 01:16:47PM -0500, Christoph Lameter wrote:
> On Wed, 2 Sep 2015, Vladimir Davydov wrote:
>
> > Slab is a kind of abnormal alloc_pages user. By calling alloc_pages_node
> > with __GFP_THISNODE and w/o __GFP_WAIT before falling back to
> > alloc
On Thu, Sep 03, 2015 at 12:32:43PM -0400, Tejun Heo wrote:
> On Wed, Sep 02, 2015 at 12:30:39PM +0300, Vladimir Davydov wrote:
> ...
> > To sum it up. Basically, there are two ways of handling kmemcg charges:
> >
> > 1. Make the memcg try_charge mimic alloc_pages be
gh order one. Both should be rare and both
aren't critical. I think I got carried away with all those obscure
"reclaimer peculiarities" at some point.
Now I think task_work reclaim initially proposed by Tejun would be a
much better fix.
I'm terribly sorry for being so ann
code cleanup.
Signed-off-by: Vladimir Davydov
---
include/linux/mm.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 6adf4167d664..30ef3b535444 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1553,8 +1553,10 @@ s
odes
and dentries are small and usually freed by RCU so not accounting them
to nr_reclaimed shouldn't make much difference. The only reason I see
why overreclaim can happen is ignoring eviction of an inode full of page
cache, speaking of which makes me wonder if it'd be better to refrain
f
On Tue, Oct 20, 2015 at 09:56:06AM -0400, Johannes Weiner wrote:
> On Tue, Oct 20, 2015 at 03:19:20PM +0300, Vladimir Davydov wrote:
> > On Mon, Oct 19, 2015 at 02:13:35PM -0400, Johannes Weiner wrote:
> > > cb731d6 ("vmscan: per memory cgroup slab shrinkers") sought to
On Thu, Oct 22, 2015 at 03:09:43PM -0400, Johannes Weiner wrote:
> On Thu, Oct 22, 2015 at 09:46:12PM +0300, Vladimir Davydov wrote:
> > On Thu, Oct 22, 2015 at 12:21:31AM -0400, Johannes Weiner wrote:
> > > The tcp memory controller has extensive provisions for future memor
On Mon, Oct 26, 2015 at 01:22:16PM -0400, Johannes Weiner wrote:
> On Thu, Oct 22, 2015 at 09:45:10PM +0300, Vladimir Davydov wrote:
> > Hi Johannes,
> >
> > On Thu, Oct 22, 2015 at 12:21:28AM -0400, Johannes Weiner wrote:
> > ...
> > > Patch #5 adds account
On Wed, Sep 30, 2015 at 12:51:18PM -0700, Greg Thelen wrote:
>
> Vladimir Davydov wrote:
...
> > diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
> > index 416509e26d6d..a190719c2f46 100644
> > --- a/include/linux/page-flags.h
> > +++ b/include/li
101 - 200 of 3498 matches
Mail list logo
