From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix extent cache fragmentation
Date: Mon, 14 Mar 2016 18:18:44 +0300 [thread overview]
Message-ID: <87h9g9ulyj.fsf@openvz.org> (raw)
In-Reply-To: <20160310043513.GC4937@thunk.org>
Theodore Ts'o <tytso@mit.edu> writes:
> On Wed, Feb 24, 2016 at 03:17:40PM +0400, Dmitry Monakhov wrote:
>> > So in principle this patch is fine but I hate how handling of extent status
>> > tree is proliferating to fs/ext4/extent.c to handle some cases especially
>> > through special function flags. So looking into the code, probably it would
>> > make sense to move all updates of the extent status tree handling down into
>> > ext4_ext_map_blocks() and ext4_ind_map_blocks(). Thoughts?
>>
>> Agree. This was my initial diea but patch was too big for stable
>> releases. In fact this is not critical fix so we can simply make is
>> in good way and simply ignore @stable. Will send updated version shortly.
>
> Hi Dmitry,
>
> Have you had a chance to come up with an updated patch?
Not yet. But I plan to do it this week.
>
> Thanks,
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-14 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 9:27 [PATCH] ext4: fix extent cache fragmentation Dmitry Monakhov
2016-02-22 14:37 ` Jan Kara
2016-02-24 11:17 ` Dmitry Monakhov
2016-03-10 4:35 ` Theodore Ts'o
2016-03-14 15:18 ` Dmitry Monakhov [this message]
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=87h9g9ulyj.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.