From: Brendan Hide <brendan@swiftspirit.co.za>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>, linux-kernel@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH v4] lib: add size unit t/p/e to memparse
Date: Fri, 13 Jun 2014 07:55:55 +0200 [thread overview]
Message-ID: <539A926B.7000204@swiftspirit.co.za> (raw)
In-Reply-To: <1402623746-1171-1-git-send-email-guihc.fnst@cn.fujitsu.com>
On 13/06/14 03:42, Gui Hecheng wrote:
> For modern filesystems such as btrfs, t/p/e size level operations
> are common.
> add size unit t/p/e parsing to memparse
>
> Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> ---
> changelog
> v1->v2: replace kilobyte with kibibyte, and others
> v2->v3: add missing unit "bytes" in comment
> v3->v4: remove idiotic name for K,M,G,P,T,E
> ---
> lib/cmdline.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/lib/cmdline.c b/lib/cmdline.c
> index d4932f7..76a712e 100644
> --- a/lib/cmdline.c
> +++ b/lib/cmdline.c
> @@ -121,11 +121,7 @@ EXPORT_SYMBOL(get_options);
> * @retptr: (output) Optional pointer to next char after parse completes
> *
> * Parses a string into a number. The number stored at @ptr is
> - * potentially suffixed with %K (for kilobytes, or 1024 bytes),
> - * %M (for megabytes, or 1048576 bytes), or %G (for gigabytes, or
> - * 1073741824). If the number is suffixed with K, M, or G, then
> - * the return value is the number multiplied by one kilobyte, one
> - * megabyte, or one gigabyte, respectively.
> + * potentially suffixed with K, M, G, T, P, E.
> */
>
> unsigned long long memparse(const char *ptr, char **retptr)
> @@ -135,6 +131,15 @@ unsigned long long memparse(const char *ptr, char **retptr)
> unsigned long long ret = simple_strtoull(ptr, &endptr, 0);
>
> switch (*endptr) {
> + case 'E':
> + case 'e':
> + ret <<= 10;
> + case 'P':
> + case 'p':
> + ret <<= 10;
> + case 'T':
> + case 't':
> + ret <<= 10;
> case 'G':
> case 'g':
> ret <<= 10;
Ah, I see - you've removed all reference to their names. That's good too. :)
--
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
next prev parent reply other threads:[~2014-06-13 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 1:42 Gui Hecheng
2014-06-13 5:55 ` Brendan Hide [this message]
2014-06-13 6:03 ` Gui Hecheng
2014-06-13 21:58 ` David Rientjes
2014-06-17 1:22 ` Gui Hecheng
2014-06-17 1:29 ` David Rientjes
2014-06-17 3:59 ` Gui Hecheng
2014-06-17 22:21 ` David Rientjes
2014-06-17 23:10 ` Satoru Takeuchi
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=539A926B.7000204@swiftspirit.co.za \
--to=brendan@swiftspirit.co.za \
--cc=akpm@linux-foundation.org \
--cc=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®