All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Timofey Titovets <nefelim4ag@gmail.com>, util-linux@vger.kernel.org
Subject: Re: [RFC] Zram handle util
Date: Mon, 21 Jul 2014 07:57:21 +0000	[thread overview]
Message-ID: <20140721075721.GC8180@gmail.com> (raw)
In-Reply-To: <1405888608.11927.11.camel@buesod1.americas.hpqcorp.net>

On Sun, Jul 20, 2014 at 01:36:48PM -0700, Davidlohr Bueso wrote:
> On Sat, 2014-07-19 at 20:28 +0300, Timofey Titovets wrote:
> > Good time of day.
> > I want hear your opinions.
> > Several days ago, i writed zramctl util (on C++) for have useful app for 
> > setup zrams..
> > Code hosted her: https://github.com/Nefelim4ag/zramctl
> > 
> > Examples:
> > zramctl find # return name of first free device (zram0)
> > zramctl find 1024M lz4 4 # (i not implement -? options now)
> > 			 # 4 - threads
> > 			 # setup and return name of device (zram1)
> > zramctl reset zram0 zram1 ...
> > 
> > 
> > I want to port it on C and try include it in util-linux, like losetup.
> > It has a sense? What do you think?
> 
> Minchan, any thoughts in keeping this sort of utility in the kernel
> tree? Perhaps tools/zram/? No idea if the code is suitable to consider
> right away, but it kinda makes sense.

First of all, Thanks for your effor, Timofey!

Adding such userspace tool in kernel src directory doesn't make sense.
If we wanted it, there are tons of user tools in kernel src directory
so IMHO, util-linux is better place.

Thanks.

> 
> Thanks,
> Davidlohr
> 

  reply	other threads:[~2014-07-21  7:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19 17:28 [RFC] Zram handle util Timofey Titovets
2014-07-19 19:12 ` Sami Kerola
     [not found]   ` <CAGqmi765JkidXDpi6bP2qUk5U7Xry5nF7y0WY4Y6M_Fq8Eiqeg@mail.gmail.com>
2014-07-19 22:44     ` Fwd: " Timofey Titovets
2014-07-20  9:38     ` Timofey Titovets
2014-07-20 20:36 ` Davidlohr Bueso
2014-07-21  7:57   ` Minchan Kim [this message]
2014-07-21  8:10     ` Karel Zak
2014-07-23 17:28 ` [RFC] [Patch] Created zramctl Timofey Titovets
2014-07-23 17:43   ` Dave Reisner
2014-07-23 17:51     ` Timofey Titovets
2014-07-24  7:29     ` Karel Zak
2014-07-24  7:26   ` Karel Zak
2014-07-24 10:23   ` Benno Schulenberg
2014-07-27 19:04 ` [RFC] [Patch v2] " Timofey Titovets
2014-08-01 10:37   ` Karel Zak
2014-08-02 14:22     ` Timofey Titovets
  -- strict thread matches above, loose matches on Subject: below --
2014-07-20 14:45 [RFC] Zram handle util Timofey Titovets
2014-07-20 15:42 ` Sami Kerola

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=20140721075721.GC8180@gmail.com \
    --to=minchan@kernel.org \
    --cc=davidlohr@hp.com \
    --cc=nefelim4ag@gmail.com \
    --cc=util-linux@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.