All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Rohner <andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
To: slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] nilfs-utils: cldconfig add an option to set minimal free blocks
Date: Mon, 20 Jan 2014 11:52:27 +0100	[thread overview]
Message-ID: <52DCFFEB.4070809@gmx.net> (raw)
In-Reply-To: <1390212899.3034.66.camel@slavad-ubuntu>

Hi Vyacheslav,

On 2014-01-20 11:14, Vyacheslav Dubeyko wrote:
> On Sun, 2014-01-19 at 15:01 +0100, Andreas Rohner wrote:
> 
> It is expected "From: <author name and name>" and "Subject: <subject>"
> in the begin of patch.

Are you sure? I don't see that in other patches and I think this
information is already contained in the email headers. I used "git
send-email" to submit the patch.

>> With this option the user can specify the minimal number of free/dead
>> blocks, which is a threshold for the GC. If there are less free blocks
>> to gain from cleaning a segment than the specified number, the GC will
>> abort and try again with a different segment.
>>
> 
> What will be under stress? I mean situation when we processed all
> segments that it is valuable for cleaning on threshold basis. Then we
> need to clean segments for space allocation but all "dirty" segments not
> reasonable choice for cleaning because of threshold.

You have a point here. I could add another option that is used when the
file system is under stress. Just like with cleaning_interval and
mc_cleaning_interval. By setting the mc-option to 0 you could disable
the threshold under stress.

> What will we have in situation when an user selects not proper value of
> threshold?

Well that's the users problem. You could also ask what will happen if
the user selects an improper min_clean_segments value ;)

> I worried about situation of skipping sibling segments from cleaning. Is
> NILFS2 driver really ready for this? Did you think about efficiency of
> free space allocation after such cleaning and about file system
> consistency? Are you sure that all will be good after such approach of
> cleaning? I simply want to be sure that you have analyzed this.

I tested it extensively and I am quite sure, that there are no problems
with that on the driver side.

Thanks for reviewing my patches,

Best regards,
Andreas Rohner
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-01-20 10:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 14:01 [PATCH 0/4] nilfs-utils: new feature to skip inefficient gc Andreas Rohner
     [not found] ` <cover.1390139797.git.andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-01-19 14:01   ` [PATCH 1/4] nilfs-utils: cldconfig add an option to set minimal free blocks Andreas Rohner
     [not found]     ` <685e5c720189d1e451ed8a0d65581aa8c5a3f7f0.1390139797.git.andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-01-20 10:14       ` Vyacheslav Dubeyko
2014-01-20 10:52         ` Andreas Rohner [this message]
     [not found]           ` <52DCFFEB.4070809-hi6Y0CQ0nG0@public.gmane.org>
2014-01-20 11:05             ` Vyacheslav Dubeyko
2014-01-20 11:13               ` Ryusuke Konishi
2014-01-20 11:55               ` Andreas Rohner
2014-01-19 14:01   ` [PATCH 2/4] nilfs-utils: cleanerd: add custom error value to enable fast retry Andreas Rohner
     [not found]     ` <a203a9d8105dc1b449e469158fb07fbffbf2da18.1390139797.git.andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-01-20 10:46       ` Vyacheslav Dubeyko
2014-01-20 12:02         ` Andreas Rohner
2014-01-19 14:01   ` [PATCH 3/4] nilfs-utils: refactoring of nilfs_reclaim_segment to add minblocks param Andreas Rohner
2014-01-19 14:01   ` [PATCH 4/4] nilfs-utils: add support for and define some nilfs_argv flags Andreas Rohner
2014-01-19 14:02   ` [PATCH] nilfs2: depending on flags, update segment usage instead of cleaning Andreas Rohner
     [not found]     ` <1390140141-4432-1-git-send-email-andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-01-19 16:49       ` Ryusuke Konishi
     [not found]         ` <20140120.014916.57469358.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-01-19 17:17           ` Andreas Rohner
2014-01-21 14:17           ` Andreas Rohner
2014-01-20  9:43   ` [PATCH 0/4] nilfs-utils: new feature to skip inefficient gc Vyacheslav Dubeyko
2014-01-20 10:37     ` Andreas Rohner
     [not found]       ` <52DCFC61.7050608-hi6Y0CQ0nG0@public.gmane.org>
2014-01-20 10:54         ` Vyacheslav Dubeyko

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=52DCFFEB.4070809@gmx.net \
    --to=andreas.rohner-hi6y0cq0ng0@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.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 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.