All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>
Cc: mitsuhiro.kimura.kc@renesas.com, f.fainelli@gmail.com,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
	galak@codeaurora.org, netdev@vger.kernel.org,
	richardcochran@gmail.com, linux-sh@vger.kernel.org,
	masaru.nagai.vx@renesas.com
Subject: Re: [PATCH v3] Renesas Ethernet AVB driver
Date: Wed, 22 Apr 2015 22:50:40 +0000	[thread overview]
Message-ID: <553825C0.2040600@cogentembedded.com> (raw)
In-Reply-To: <20150422.184133.132510003688162502.davem@davemloft.net>

On 04/23/2015 01:41 AM, David Miller wrote:


>>     Sigh... I'm seeing no way out of that then, only copying. :-(

> What exactly is the device's restriction?

    The frame data must be aligned on 32-bit boundary.

> Any reasonable modern chip allows one of two things.

> Either it allows arbitrary alignment of the start of the TX
> frame when DMA'ing.

> _or_

> It allows a variable number of pad bytes to be inserted by the
> driver before giving it to the card, which do not go onto the
> wire, in order to meet the device's DMA restrictions.

> For example, if the packet is only 2 byte aligned, you set the "ignore
> offset" to 2 and push two zero bytes in front of the ethernet frame
> before giving it to the card.

    I'm not seeing any padding logic on the TX path, only on the RX path (but 
it counts in 4-byte words, so seems quite useless).

> If a chip made in this day and era cannot do one of those two things,
> this is beyond disappointing and is a massive engineering failure.
> Whoever designed this chip made no investigation into how their
> hardware is going to be actually used.

    Too nad the Renesas SoC designers are not reading that. :-)

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>
Cc: mitsuhiro.kimura.kc@renesas.com, f.fainelli@gmail.com,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
	galak@codeaurora.org, netdev@vger.kernel.org,
	richardcochran@gmail.com, linux-sh@vger.kernel.org,
	masaru.nagai.vx@renesas.com
Subject: Re: [PATCH v3] Renesas Ethernet AVB driver
Date: Thu, 23 Apr 2015 01:50:40 +0300	[thread overview]
Message-ID: <553825C0.2040600@cogentembedded.com> (raw)
In-Reply-To: <20150422.184133.132510003688162502.davem@davemloft.net>

On 04/23/2015 01:41 AM, David Miller wrote:


>>     Sigh... I'm seeing no way out of that then, only copying. :-(

> What exactly is the device's restriction?

    The frame data must be aligned on 32-bit boundary.

> Any reasonable modern chip allows one of two things.

> Either it allows arbitrary alignment of the start of the TX
> frame when DMA'ing.

> _or_

> It allows a variable number of pad bytes to be inserted by the
> driver before giving it to the card, which do not go onto the
> wire, in order to meet the device's DMA restrictions.

> For example, if the packet is only 2 byte aligned, you set the "ignore
> offset" to 2 and push two zero bytes in front of the ethernet frame
> before giving it to the card.

    I'm not seeing any padding logic on the TX path, only on the RX path (but 
it counts in 4-byte words, so seems quite useless).

> If a chip made in this day and era cannot do one of those two things,
> this is beyond disappointing and is a massive engineering failure.
> Whoever designed this chip made no investigation into how their
> hardware is going to be actually used.

    Too nad the Renesas SoC designers are not reading that. :-)

WBR, Sergei


  reply	other threads:[~2015-04-22 22:50 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 22:07 [PATCH v3] Renesas Ethernet AVB driver Sergei Shtylyov
2015-04-13 22:07 ` Sergei Shtylyov
2015-04-13 22:38 ` Florian Fainelli
2015-04-13 22:38   ` Florian Fainelli
2015-04-14 21:37   ` Sergei Shtylyov
2015-04-14 21:37     ` Sergei Shtylyov
2015-04-22  5:04     ` MITSUHIRO KIMURA
2015-04-22  5:04       ` MITSUHIRO KIMURA
2015-04-22 15:36       ` David Miller
2015-04-22 15:36         ` David Miller
2015-04-22 20:30         ` Sergei Shtylyov
2015-04-22 20:30           ` Sergei Shtylyov
2015-04-22 20:42           ` David Miller
2015-04-22 20:42             ` David Miller
2015-04-22 20:46             ` Sergei Shtylyov
2015-04-22 20:46               ` Sergei Shtylyov
2015-04-22 22:17               ` David Miller
2015-04-22 22:17                 ` David Miller
2015-04-22 21:38             ` Sergei Shtylyov
2015-04-22 21:38               ` Sergei Shtylyov
2015-04-22 22:18               ` David Miller
2015-04-22 22:18                 ` David Miller
2015-04-22 22:34                 ` Sergei Shtylyov
2015-04-22 22:34                   ` Sergei Shtylyov
2015-04-22 22:41                   ` David Miller
2015-04-22 22:41                     ` David Miller
2015-04-22 22:50                     ` Sergei Shtylyov [this message]
2015-04-22 22:50                       ` Sergei Shtylyov
2015-04-24  9:03               ` David Laight
2015-04-24 18:27                 ` Sergei Shtylyov
2015-04-24 18:27                   ` Sergei Shtylyov
2015-04-27  9:22                   ` David Laight
2015-04-22 23:22     ` Florian Fainelli
2015-04-22 23:22       ` Florian Fainelli
2015-04-24 18:53       ` Sergei Shtylyov
2015-04-24 18:53         ` Sergei Shtylyov
2015-04-28 17:09         ` Ben Hutchings
2015-04-28 17:09           ` Ben Hutchings
2015-05-07 21:10         ` Sergei Shtylyov
2015-05-07 21:10           ` Sergei Shtylyov
2015-05-07 21:25           ` Sergei Shtylyov
2015-05-07 21:25             ` Sergei Shtylyov
2015-04-14  0:49 ` Lino Sanfilippo
2015-04-14  0:49   ` Lino Sanfilippo
2015-04-14 11:31   ` David Laight
2015-04-19 22:10   ` Sergei Shtylyov
2015-04-19 22:10     ` Sergei Shtylyov
2015-04-19 23:45     ` Lino Sanfilippo
2015-04-19 23:45       ` Lino Sanfilippo
2015-04-19  9:19 ` Richard Cochran
2015-04-19  9:19   ` Richard Cochran

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=553825C0.2040600@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-sh@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masaru.nagai.vx@renesas.com \
    --cc=mitsuhiro.kimura.kc@renesas.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=richardcochran@gmail.com \
    --cc=robh+dt@kernel.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.