Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: "Andrew.an" <bh74.an@samsung.com>
Cc: netdev@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	davem@davemloft.net, ilho215.lee@samsung.com,
	siva.kallam@samsung.com, vipul.pandya@samsung.com,
	ks.giri@samsung.com, 'Joe Perches' <joe@perches.com>
Subject: Re: [PATCH V2 RE-SEND 1/7] net: sxgbe: add basic framework for Samsung 10Gb ethernet driver
Date: Mon, 17 Mar 2014 00:11:01 +0100	[thread overview]
Message-ID: <20140316231101.GA23765@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <000e01cf40ac$08c19290$1a44b7b0$@samsung.com>

Andrew.an <bh74.an@samsung.com> :
[...]
> > > +struct sxgbe_core_ops {
> > > +	/* MAC core initialization */
> > > +	void (*core_init)(void __iomem *ioaddr);
[...]
> > > +	/* adjust SXGBE speed */
> > > +	void (*set_speed)(void __iomem *ioaddr, unsigned char speed);
> > > +};
> > 
> > This indirection level is never used.
> Those are used, can you give more detail?

They are used but they always point to the same set of methods.
Those methods could thus be directly called.

[...]
> > > +/* SXGBE private data structures */
> > > +struct sxgbe_tx_queue {
> > > +	u8 queue_no;
> > > +	unsigned int irq_no;
> > > +	struct sxgbe_priv_data *priv_ptr;
> > > +	struct sxgbe_tx_norm_desc *dma_tx;
> > 
> > You may lay things a bit differently.
> can you give more detail?

Bigger fields first, u8 at the end. It will save padding in the struct.

-- 
Ueimor

  reply	other threads:[~2014-03-16 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  6:55 [PATCH V2 RE-SEND 1/7] net: sxgbe: add basic framework for Samsung 10Gb ethernet driver Byungho An
2014-03-13 12:53 ` Joe Perches
2014-03-13 13:02   ` Joe Perches
2014-03-14  0:44 ` Francois Romieu
2014-03-16  0:09   ` Andrew.an
2014-03-16 23:11     ` Francois Romieu [this message]
2014-03-17  3:53       ` Byungho An
2014-03-17 16:58         ` Stephen Hemminger
2014-03-17 17:38           ` Byungho An

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=20140316231101.GA23765@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=bh74.an@samsung.com \
    --cc=davem@davemloft.net \
    --cc=ilho215.lee@samsung.com \
    --cc=joe@perches.com \
    --cc=ks.giri@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=siva.kallam@samsung.com \
    --cc=vipul.pandya@samsung.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