All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-btrfs@vger.kernel.org>, <1i5t5.duncan@cox.net>,
	Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Subject: [PATCH v3] lib: add size unit t/p/e to memparse
Date: Wed, 2 Apr 2014 16:54:37 +0800	[thread overview]
Message-ID: <1396428877-24089-1-git-send-email-guihc.fnst@cn.fujitsu.com> (raw)

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
---
 lib/cmdline.c | 25 ++++++++++++++++++++-----
 1 file changed, 20 insertions(+), 5 deletions(-)

diff --git a/lib/cmdline.c b/lib/cmdline.c
index eb67911..511b9be 100644
--- a/lib/cmdline.c
+++ b/lib/cmdline.c
@@ -119,11 +119,17 @@ char *get_options(const char *str, int nints, int *ints)
  *	@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 (for kibibytes, or 1024 bytes),
+ *	%M (for mebibytes, or 1048576 bytes),
+ *	%G (for gibibytes, or 1073741824 bytes),
+ *	%T (for tebibytes, or 1099511627776 bytes),
+ *	%P (for pebibytes, or 1125899906842624 bytes),
+ *	%E (for exbibytes, or 1152921504606846976 bytes).
+ *	If the number is suffixed with K, M, G, T, P, E, then
+ *	the return value is the number multiplied by one kibibyte, one
+ *	mebibyte, one gibibyte, one tebibyte, one pebibyte, one exbibyte,
+ *	respectively.
  */
 
 unsigned long long memparse(const char *ptr, char **retptr)
@@ -133,6 +139,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;
-- 
1.8.1.4


             reply	other threads:[~2014-04-02  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02  8:54 Gui Hecheng [this message]
2014-05-15  1:39 ` [ping][PATCH v3] lib: add size unit t/p/e to memparse Gui Hecheng
2014-06-05  9:03 ` ·[ping][PATCH " Gui Hecheng
2014-06-12 21:15 ` [PATCH " Andrew Morton
2014-06-13  1:33   ` Gui Hecheng
2014-06-13  5:54   ` Brendan Hide
2014-06-13  6:56     ` Hugo Mills

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=1396428877-24089-1-git-send-email-guihc.fnst@cn.fujitsu.com \
    --to=guihc.fnst@cn.fujitsu.com \
    --cc=1i5t5.duncan@cox.net \
    --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 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.