From: Robert Hancock <hancockrwd@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: ide <linux-ide@vger.kernel.org>, Jeff Garzik <jeff@garzik.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH #upstream] libata: enhance command parsing
Date: Fri, 28 Aug 2009 17:55:35 -0600 [thread overview]
Message-ID: <4A986E77.9040000@gmail.com> (raw)
In-Reply-To: <4A905A4E.5000309@rtr.ca>
On 08/22/2009 02:51 PM, Mark Lord wrote:
>> Actually, I think the code+data size of this version is not much
>> different from the previous version. One might be able to come up with
>> a structure that you could encapsulate all the strings into and that
>> you could search through to find the right one, but it'd be tricky to
>> do that without making the structure end up containing a bunch of
>> padding and other wasted space that would add as much data size as you
>> saved in code size. Unless you have a great idea on the subject that
>> I'm not thinking of right after waking up :-)
> ..
>
> I've done lots of this type of thing in the past,
> putting the parsing knowledge into the data structure
> and reducing the code to nearly nothing (at the expense
> of more data than before).
>
> But right now I'm not offering to do it, so no objection
> from me to the current state. :)
Any other thoughts on this one? Jeff?
prev parent reply other threads:[~2009-08-29 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 21:27 [PATCH #upstream] libata: enhance command parsing Robert Hancock
2009-08-22 5:57 ` Robert Hancock
2009-08-22 14:02 ` Mark Lord
[not found] ` <4A8FFA44.30604@rtr.ca>
[not found] ` <51f3faa70908220936w309d9754p4f96cee44d58ea63@mail.gmail.com>
[not found] ` <4A905A4E.5000309@rtr.ca>
2009-08-28 23:55 ` Robert Hancock [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=4A986E77.9040000@gmail.com \
--to=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).