From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Dušan Čolić" <dusanc@gmail.com>,
reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: [RFC] Smart fibration plugin ext_4321
Date: Mon, 26 Dec 2016 20:47:30 +0200 [thread overview]
Message-ID: <586165C2.3000702@gmail.com> (raw)
In-Reply-To: <CADW=+3=Vwi1LFJn8imp7H6woiRP2Oa0=Q=_K-dDqc=hc2cOkZg@mail.gmail.com>
On 12/25/2016 02:59 AM, Dušan Čolić wrote:
> Fibration is a great way to decrease fragmentation and increase throughput.
> Currently there are 4 fibration plugins, lex, dot.o, ext_1 and ext_3
> and they all have their upsides and downsides.
>
> Proposed fibration plugin combines them all so that it combines files
> with same extensions for 1, 2. 3 and 4 character extension in groups
> and sorts them in same fiber group.
>
> With this fibration plugin all eg. xvid files would be in same group
> in folder on disk sorted alphabetically
What application wants all xvid files to be in the same group?
Do you have any benchmark numbers which show advantages
of the new plugin?
Thanks,
Edward.
> so that we will avoid putting
> small files between them and in that way reduce fragmentation. That
> group (xvid 4 character extensions) would be among last groups under
> one directory so that all small files would be written before it.
>
> Problem with the attached patch is that currently every fibre value is
> defined as u64 (eg. static __u64 fibre_ext_3) but if I understood
> correctly comments in kassign.c and fibration.c fibration part of the
> key is only 7 bits long.
> If that is true how did fibre_ext_3 worked?
>
> Thanks
>
> Dushan
next prev parent reply other threads:[~2016-12-26 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 0:59 [RFC] Smart fibration plugin ext_4321 Dušan Čolić
2016-12-25 8:51 ` Dušan Čolić
2016-12-26 18:47 ` Edward Shishkin [this message]
2016-12-26 21:13 ` Dušan Čolić
2017-01-06 13:44 ` Edward Shishkin
2017-01-06 15:34 ` Dušan Čolić
2017-01-06 19:58 ` Edward Shishkin
2017-01-06 23:09 ` Dušan Čolić
2017-01-06 23:05 ` Edward Shishkin
2017-01-07 8:15 ` Dušan Čolić
2017-01-07 7:58 ` Edward Shishkin
2017-01-07 17:10 ` Dušan Čolić
2017-01-07 17:56 ` Edward Shishkin
2017-01-07 19:26 ` Dušan Čolić
2017-01-07 19:06 ` Edward Shishkin
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=586165C2.3000702@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dusanc@gmail.com \
--cc=reiserfs-devel@vger.kernel.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.