From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "Dan Kegel" <dank@kegel.com>, "Luck, Tony" <tony.luck@intel.com>
Cc: "Mikulas Patocka" <mikulas@artax.karlin.mff.cuni.cz>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
<linux-aio@kvack.org>
Subject: RE: Redundant memset in AIO read_events
Date: Wed, 9 Jul 2003 15:43:06 -0700 [thread overview]
Message-ID: <41F331DBE1178346A6F30D7CF124B24B2A488C@fmsmsx409.fm.intel.com> (raw)
> <newbie>
> There might be some architecture that requires 16 byte alignment...
> how about surrounding the memcpy with
> if (sizeof(struct io_event) != 4 * sizeof(__u64)) ?
> </newbie>
The point I'm trying to make is that it is irrelevant with respect to
alignment, size, or padding. memset and struct copying has the same
length and destination address. Why bother with the memset? It's the
same as writing a code like this:
blah = 0;
blah = foo;
- Ken
next reply other threads:[~2003-07-09 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 22:43 Chen, Kenneth W [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 22:41 Chen, Kenneth W
2003-07-09 15:43 Luck, Tony
2003-07-09 16:13 ` Dan Kegel
2003-07-08 23:17 Chen, Kenneth W
2003-07-09 12:55 ` Mikulas Patocka
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=41F331DBE1178346A6F30D7CF124B24B2A488C@fmsmsx409.fm.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=dank@kegel.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®