All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dmcache project
Date: Sat, 10 Oct 2009 22:02:16 +0100	[thread overview]
Message-ID: <20091010210216.GD19397@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4bbcfcd40910101336t4cf3824bsf6fb58e12c350953@mail.gmail.com>

On Sun, Oct 11, 2009 at 02:06:41AM +0530, ganesh kumar wrote:
>       I am working on the dmcacheio project which is described in the
> http://kernelnewbies.org/KernelProjects/DmCache.I am newbie to he
> kernel modules..kindly give me the ideas to implement the project
> through device mapper.hoping replies
 
Quite a difficult project in my opinion.

I'd suggest first isolating some features that you believe would
contribute to a solution to part of the stated problem and implementing
them as building blocks to use later.   Above that, a complex tunable
logic layer (mostly in userspace perhaps) making the decisions about
which building blocks to use and how to connect and tune them based on
live system information and feedback from small changes it attempts
('experiments') to see if they make the system perform better or worse
(based on clear configurable criteria you'll need to develop).

Start by understanding what we have in dm targets already - both
upstream (snapshots, multipath) and not yet upstream (replication,
raid45, iostats, shared snapshots) and consider ways of hooking into
relevant parts of that by improving or extending interfaces.  (You may
discover some of the building blocks and interfaces you need already
exist.)

Alasdair

  reply	other threads:[~2009-10-10 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 20:36 dmcache project ganesh kumar
2009-10-10 21:02 ` Alasdair G Kergon [this message]
2009-10-12 19:47 ` Wes Felter

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=20091010210216.GD19397@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    /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.