2013/5/27, Jaegeuk Kim :
> Hi Namjae,
Hi Jaegeuk.
First, Thanks for your interest.
>
> This is an interesting functionality.
> Could you describe why and when we need to do this?
> What are pros and cons?
> How can we use this?
As the default size of the F2FS parameter can vary as per the storage
Hi,
Thank you for the report.
I'm not able to reproduce this at all.
In my runs, there was no regression.
Can you do that?
Thanks,
2013-05-15 (수), 12:09 +0300, Anca Emanuel:
> Regresions:
> http://www.phoronix.com/scan.php?page=article&item=linux_310_f2fs&num=3
>
> The most notable one is Postg
Hi Namjae,
This is an interesting functionality.
Could you describe why and when we need to do this?
What are pros and cons?
How can we use this?
IMO, when users try to control IO latencies, it seems that they can
trigger such the explicit GCs, but in order to do that, they also need
to know the
On Sun, May 26, 2013 at 05:05:15PM +0200, walter harms wrote:
>
>
> Am 23.05.2013 12:02, schrieb Dan Carpenter:
> > There is an error path where "dir" is an ERR_PTR.
> >
> > Signed-off-by: Dan Carpenter
> >
> > diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> > index 5148d90..921aede 100
Am 23.05.2013 12:02, schrieb Dan Carpenter:
> There is an error path where "dir" is an ERR_PTR.
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> index 5148d90..921aede 100644
> --- a/fs/f2fs/recovery.c
> +++ b/fs/f2fs/recovery.c
> @@ -71,7 +71,8 @@ st
