From: Randy Dunlap <randy.dunlap@oracle.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-mm@kvack.org, akpm <akpm@linux-foundation.org>
Subject: Re: [RFC/PATCH v2] shmem: use lib/parser for mount options
Date: Thu, 7 Jun 2007 13:12:12 -0700 [thread overview]
Message-ID: <20070607131212.6d187fdd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706071940340.32729@blonde.wat.veritas.com>
On Thu, 7 Jun 2007 19:57:18 +0100 (BST) Hugh Dickins wrote:
> On Tue, 5 Jun 2007, Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > Convert shmem (tmpfs) to use the in-kernel mount options parsing library.
> >
> > Old size: 0x368 = 872 bytes
> > New size: 0x3b6 = 950 bytes
>
> Varies with arch/config: in some cases the old is smaller,
> in other cases your new. And you're not accounting for (nor
> drawing attention to) any bugfixes you added (nor, for that matter,
> on any bugs you added - but we usually keep quiet about those ;)
>
> > If you feel that there is no significant advantage to this, that's OK,
> > I can just drop it.
>
> Hmm. Hmm. My own personal feeling is that it's not really an
> improvement; especially the Opt_mpol block (and the unnecessary
> is_remount arg I already commented on).
Yes, I reread that comment earlier today.
The mpol=args parameter string is messy, due to the commas that
may be in it, whereas the old & new parsers like to split options
at commas.
> But I'm familiar with what's already there: I'd happily be overruled
> on this if others feel yours really is an improvement. Anyone?
> And you've cleaned up that "no space after comma" coding style.
>
> For me, the main question is, did you fix any bugs? You certainly
> discovered the nonline mpol crash, which was worthwhile in itself.
> And you've discovered that memparse accepts k, M, G without a digit:
> if it treated that as 1 I wouldn't mind so much, but it treats it as 0.
Right. memparse could be fixed, or lib/parser.c could gain some
additions/extensions, such as support for memparse and long long
option values. I think that those would be useful additions.
> We can live with that; but if we're to fix it, I'd prefer the fix to
> go into memparse itself - though it's called from many places, so
> maybe there's an audit job to see if the present behaviour could
> make sense in any of them.
>
> Hugh
I can't convince myself that it's worth the change... :)
Thanks for looking.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-06-07 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 7:00 [RFC/PATCH 2/2] " Randy Dunlap
2007-05-29 16:23 ` Hugh Dickins
2007-06-05 22:35 ` [RFC/PATCH v2] " Randy Dunlap, Randy Dunlap
2007-06-07 18:57 ` Hugh Dickins
2007-06-07 20:12 ` Randy Dunlap [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=20070607131212.6d187fdd.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.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