All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] lustre: TODO updated?
Date: Mon, 19 Oct 2015 14:33:28 +0200	[thread overview]
Message-ID: <5624E318.2000302@gmail.com> (raw)
In-Reply-To: <E50244C5-9F99-49A9-9FF6-96527BD0BE9C@intel.com>

On 10/15/2015 08:55 PM, Drokin, Oleg wrote:

> Yes, it's still accurate from 10.000 ft view.
> 
> If you need some more detailed ideas, here's my current list of stuff:
> 
>  getting rid of remaining lustre allocation macros: OBD_SLAB_ALLOC/FREE and friends much like we got rid of
>  OBD_ALLOC/FREE before.
>  I think LIBCFS_ALLOC/FREE and friends would need the same treatment.
> 
>  I bet there are other wrapping functions (from libcfs compat code and such)
>  that need to be removed.
> 
>  typedefs: we did remove some, there are more left that need to be taken care of.
> 
>  Coding style - we are much better now here and the work is ongoing by a lot of
>  other people.
> 
>  Function defines - need to be looked into.
> 
>  In addition, more involved ones:
> 
>  After that there are more laborous ones like figuring out how to fit into the
>  perf framework as one example.
> 
>  Also we need to rip remaining parts of server code that is still present greatly there
>  (one example - oti handle users are either server only or client only with dummy
>   handle - in echo code only. These could be greatly pruned.
>   Then we can cleanup all the obd method tables to remove now unused pointers and so on).

Could you please reflect these things in TODO file ?

-thanks-

      reply	other threads:[~2015-10-19 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <561CF52C.2070806@gmail.com>
2015-10-15 18:55 ` [lustre-devel] lustre: TODO updated? Drokin, Oleg
2015-10-19 12:33   ` Xose Vazquez Perez [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=5624E318.2000302@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=lustre-devel@lists.lustre.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.