linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Vdovichev <ext-alexander.vdovichev@nokia.com>
To: ext Tomasz Torcz <tomek@pipebreaker.pl>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Question about specific patch (eMMC)
Date: Wed, 01 Sep 2010 11:31:59 +0300	[thread overview]
Message-ID: <1283329919.3347.17.camel@calladain.research.nokia.com> (raw)
In-Reply-To: <20100831172715.GA14509@mother.pipebreaker.pl>

Hi,
On Tue, 2010-08-31 at 19:27 +0200, ext Tomasz Torcz wrote:
> On Tue, Aug 31, 2010 at 02:57:05PM +0300, Alexander Vdovichev wrote:
> > Hello all,
> > Is there any patches for btrfs to use enhanced area in eMMC (it will
> > allow to boost performance i.e. it very useful to keep metadata within
> > this area) ?
> > 
> > If it's exist let me know how to find it and use it.
> 
>   I'm not aware of this at the moment.  However, there are data-temperature
> tracking patches.  Their point is to move hot data into faster storage.
Could you point me where I can find it ?
> I believe they can grow into generic infrastructure to inform filesystems
> about non-homogenous nature of underlaying storage.
I guess that it will require specific patches to the filesystem.
Each filesystem has a specific policy to locate metadata, but most
manufacturers believe that the device will use fat filesystem and they
creates special areas to keep fat metadata (allocation table).
If btrfs will has an option to use this area it will be a good advantage
to use it in embedded area.

Thanks,




      reply	other threads:[~2010-09-01  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 11:57 Question about specific patch (eMMC) Alexander Vdovichev
2010-08-31 17:27 ` Tomasz Torcz
2010-09-01  8:31   ` Alexander Vdovichev [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=1283329919.3347.17.camel@calladain.research.nokia.com \
    --to=ext-alexander.vdovichev@nokia.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tomek@pipebreaker.pl \
    /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;
as well as URLs for NNTP newsgroup(s).