All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] network mega patch
Date: Fri, 04 May 2012 08:07:49 +0200	[thread overview]
Message-ID: <4FA37235.8030608@gmail.com> (raw)
In-Reply-To: <CAF-6-Q3Xa9B-rXxi0H-FeSE80toDHWOw8n6oRh0v3L2_mXEwmw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

On 04.05.2012 05:43, Bean wrote:
> On Fri, May 4, 2012 at 3:50 AM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> On 03.05.2012 21:40, Bean wrote:
>>> +  if (rsm->asm_netbuff)
>>> +    grub_netbuff_free (rsm->asm_netbuff);
>>  Could you make grub_netbuff_free skip on NULL and so simplify it here?
> Hi,
>
> I think this is one of the few place where netbuff can be NULL (it
> usually return error when grub_netbuff_alloc return NULL), since
> grub_netbuff_free is called a lot, it might have a little performance
> impact when we do the check in grub_netbuff_free.
It's not called that much that this additional check would be a
performance hit. But it decreases the probability of similar bugs to
essentially zero.
>> When you've done this you can commit bug.diff.
>> Thank you
>>
>> --
>> Regards
>> Vladimir 'φ-coder/phcoder' Serbinenko
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2012-05-04  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 19:19 [PATCH] network mega patch Bean
2012-05-03 19:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-03 19:40   ` Bean
2012-05-03 19:50     ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-04  3:43       ` Bean
2012-05-04  6:07         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-05-04  7:04           ` Bean

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=4FA37235.8030608@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.