From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] lib: include rte_memory.h for __rte_cache_aligned
Date: Thu, 11 Dec 2014 09:17:27 -0500 [thread overview]
Message-ID: <20141211141727.GC28213@hmsreliant.think-freely.org> (raw)
In-Reply-To: <30845403.kPBAiWVWY3@xps13>
On Thu, Dec 11, 2014 at 01:36:54AM +0100, Thomas Monjalon wrote:
> Hi Neil,
>
> 2014-12-10 19:28, Neil Horman:
> > On Wed, Dec 10, 2014 at 07:09:03PM +0000, Jia Yu wrote:
> > > Hi Neil,
> > >
> > > Moving __rte_cache_aligned right after struct keyword will help. On the
> > > other hand, enforcing this rule for existing (100+) and future definitions
> > > will be difficult. It¹s clearer and a good practice to include header file
> > > explicitly.
> > >
> > You need to include the header file regardless of what you do. The advantage to
> > placing the macro right after the struct keyword is that failure to include the
> > header will result in a compiler error, rather than silent behavioral changes
> > and run time breakage.
> >
> > You don't have to enforce putting the attribute after the struct keyword, I'd
> > say just move them now to protect the current code. Subsequent patch authors
> > will see the existing style and follow suit. Or they won't, and we'll point out
> > the issue during review.
>
> It should be a different patch for next release cycle.
> Let's apply this fix only for 1.8.0.
>
Why? Theres no harm in doing so now.
Neil
next prev parent reply other threads:[~2014-12-11 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 17:28 [dpdk-dev] [PATCH] " Jia Yu
2014-11-10 9:46 ` Thomas Monjalon
2014-11-17 19:07 ` Jia Yu
2014-12-08 15:04 ` [dpdk-dev] " Neil Horman
2014-12-09 8:53 ` Olivier MATZ
2014-12-09 9:11 ` Jia Yu
2014-12-09 15:22 ` Neil Horman
2014-12-10 19:09 ` Jia Yu
2014-12-11 0:28 ` Neil Horman
2014-12-11 0:36 ` Thomas Monjalon
2014-12-11 14:17 ` Neil Horman [this message]
2014-12-11 21:14 ` Thomas Monjalon
2014-12-11 0:51 ` Thomas Monjalon
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=20141211141727.GC28213@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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;
as well as URLs for NNTP newsgroup(s).