All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Salah Triki <salah.triki@acm.org>,
	ngupta@vflare.org, linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH 0/3] zram: Replace pr_* with dev_*
Date: Fri, 7 Aug 2015 15:56:11 +0900	[thread overview]
Message-ID: <20150807065611.GI1891@swordfish> (raw)
In-Reply-To: <20150807063756.GH1891@swordfish>

On (08/07/15 15:37), Sergey Senozhatsky wrote:
[..]
> we now have errors like
>  'zram: Cannot initialise lzo compressing backend'
> 
> and they will transform into
> 
>  'block zram0: Cannot initialise lzo compressing backend'
> 
> note the prefix 'zram:' became 'block zram0:'

but it doesn't come for free. where we had clean and nice

pr_err("Decompression failed!...
pr_info("Unable to allocate temp memory\n"...
etc...

now we have monsters

dev_err(disk_to_dev(zram->disk), "Decompression failed!...
dev_info(disk_to_dev(zram->disk), "Unable to allocate temp memory\n"...
etc.


other changes are very questionable... for example

   pr_info("Added device: %s\n", zram->disk->disk_name);
becomes
   dev_info(disk_to_dev(zram->disk), "Added device: %s\n", zram->disk->disk_name);


why? there is no reason to do this!



and messages are converted in a bit random manner, shall I say. so now
we have a mix of dev_* and pr_* errors. to convert them all to dev_* (which
is not possible in all the cases) we would need to change some function
prototypes and start passing zram pointer, or disk...

example:

static struct zram_meta *zram_meta_alloc(int device_id, u64 disksize)
{
        size_t num_pages;
        char pool_name[8];
        struct zram_meta *meta = kmalloc(sizeof(*meta), GFP_KERNEL);

        if (!meta)
                return NULL;

        num_pages = disksize >> PAGE_SHIFT;
        meta->table = vzalloc(num_pages * sizeof(*meta->table));
        if (!meta->table) {
                pr_err("Error allocating zram address table\n");
                goto out_error;
        }

        snprintf(pool_name, sizeof(pool_name), "zram%d", device_id);
        meta->mem_pool = zs_create_pool(pool_name, GFP_NOIO | __GFP_HIGHMEM);
        if (!meta->mem_pool) {
                pr_err("Error creating memory pool\n");
                goto out_error;
        }
...



so I see a little value. really. too much things to change.

	-ss

  reply	other threads:[~2015-08-07  6:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 22:57 [PATCH 0/3] zram: Replace pr_* with dev_* Salah Triki
2015-08-06 23:03 ` [PATCH 1/3] zram: Replace pr_info with dev_info in max_comp_streams_store Salah Triki
2015-08-06 23:03   ` [PATCH 2/3] zram: Replace pr_info with dev_info in comp_algorithm_store Salah Triki
2015-08-06 23:03     ` [PATCH 3/3] zram: Replace pr_* with dev_* Salah Triki
2015-08-07  0:05 ` [PATCH 0/3] " Sergey Senozhatsky
2015-08-07  1:17   ` Joe Perches
2015-08-07  1:42     ` Sergey Senozhatsky
2015-08-07  1:48       ` Joe Perches
2015-08-07  2:03         ` Sergey Senozhatsky
2015-08-07  2:16           ` Sergey Senozhatsky
2015-08-07  6:05   ` Minchan Kim
2015-08-07  6:37     ` Sergey Senozhatsky
2015-08-07  6:56       ` Sergey Senozhatsky [this message]
2015-08-07  7:12         ` Joe Perches
2015-08-07  7:25           ` Sergey Senozhatsky
2015-08-07 14:58       ` Minchan Kim
2015-08-10  1:25         ` Sergey Senozhatsky

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=20150807065611.GI1891@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=salah.triki@acm.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.