From: Jens Axboe <[email protected]>
To: Wu Bo <[email protected]>
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [PATCH] io_uring: NULL check before kfree() is not needed
Date: Fri, 14 Aug 2020 20:39:31 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 8/14/20 8:25 PM, Wu Bo wrote:
> NULL check before kfree() is not needed
While it's not needed, it's also slower. Particularly on AMD it seems.
It's on my list to ensure that kfree() is an inline that checks for
non-NULL before calling the real freeing function.
Should get around to that soon, as this is probably the third time
someone has sent this patch :-)
--
Jens Axboe
prev parent reply other threads:[~2020-08-15 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 3:25 [PATCH] io_uring: NULL check before kfree() is not needed Wu Bo
2020-08-15 3:39 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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