From: Chandan Vn <vn.chandan@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org
Subject: Re: Requesting to share current work items
Date: Sat, 7 Apr 2018 09:48:54 +0530 [thread overview]
Message-ID: <CADYJ94c7YKG3txKMpufVUhSjV8r0WpB6NFiOWUutex+oQ-fwNA@mail.gmail.com> (raw)
In-Reply-To: <20180406205828.GA9618@bombadil.infradead.org>
On Sat, Apr 7, 2018 at 2:28 AM, Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Apr 06, 2018 at 07:20:47AM +0000, Chandan Vn wrote:
>> Hi,
>>
>> I would like to start contributing to linux-mm community.
>> Could you please let me know the current work items which I can start
>> working on.
>>
>> Please note that I have been working on linux-mm from past 4 years but
>> mostly proprietary or not yet mainlined vendor codebase.
>
> We had a report of a problem a few weeks ago that I don't know if anybody
> is looking at yet. Perhaps you'd like to try fixing it.
>
> The report says that, under some unidentified workload, calling vmalloc
> can take many hundreds of milliseconds, and the problem is in
> alloc_vmap_area().
>
> So a good plan of work would be to devise a kernel module which can
> produce a highly-fragmented vmap area, and demonstrate the problem.
> Once you've got a reliable reproducer, you can look at how to fix this
> problem. We probably need a better data structure; either enhance
> the existing rbtree of free areas, or change the data structure.
Sure. I would work on this.
next prev parent reply other threads:[~2018-04-07 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 7:20 Chandan Vn
2018-04-06 20:58 ` Matthew Wilcox
2018-04-07 4:18 ` Chandan Vn [this message]
2018-04-13 9:15 ` Anshuman Khandual
2018-04-13 10:23 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADYJ94c7YKG3txKMpufVUhSjV8r0WpB6NFiOWUutex+oQ-fwNA@mail.gmail.com \
--to=vn.chandan@gmail.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox