From: "fugang.duan@freescale.com" <fugang.duan@freescale.com>
To: David Miller <davem@davemloft.net>,
"romieu@fr.zoreil.com" <romieu@fr.zoreil.com>
Cc: "Frank.Li@freescale.com" <Frank.Li@freescale.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>
Subject: RE: [PATCH] net: fec: remove memory copy for rx path
Date: Sun, 28 Sep 2014 03:30:47 +0000 [thread overview]
Message-ID: <65add7b63c4e41e49ef019bd58bbf404@BY2PR03MB377.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20140927.185600.1057301078747765304.davem@davemloft.net>
From: David Miller <davem@davemloft.net> Sent: Sunday, September 28, 2014 6:56 AM
>To: romieu@fr.zoreil.com
>Cc: Duan Fugang-B38611; Li Frank-B20596; netdev@vger.kernel.org;
>shawn.guo@linaro.org; bhutchings@solarflare.com
>Subject: Re: [PATCH] net: fec: remove memory copy for rx path
>
>From: Francois Romieu <romieu@fr.zoreil.com>
>Date: Sat, 27 Sep 2014 13:39:37 +0200
>
>> fugang.duan@freescale.com <fugang.duan@freescale.com> :
>>> From: David Miller <davem@davemloft.net> Sent: Saturday, September
>>> 27, 2014 5:07 AM
>> [...]
>>> >We call this rx_copybreak, and there are many drivers you can look
>>> >at to see how this works.
>>> >
>>> >Thanks.
>>>
>>> Great suggestion. I will change it for next version.
>>
>> Be aware that copybreak module option should be considered legacy.
>>
>> There is an ethtool api for it.
>
>Right.
Got it, thanks David and romieu.
Regards,
Andy
prev parent reply other threads:[~2014-09-28 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 6:05 [PATCH] net: fec: remove memory copy for rx path Fugang Duan
2014-09-26 21:07 ` David Miller
2014-09-27 9:15 ` fugang.duan
2014-09-27 11:39 ` Francois Romieu
2014-09-27 22:56 ` David Miller
2014-09-28 3:30 ` fugang.duan [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 \
--in-reply-to=65add7b63c4e41e49ef019bd58bbf404@BY2PR03MB377.namprd03.prod.outlook.com \
--to=fugang.duan@freescale.com \
--cc=Frank.Li@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shawn.guo@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox