From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <peppe.cavallaro@st.com>, <seraphin.bonnaffe@st.com>,
<hock.leong.kweh@intel.com>, <niklas.cassel@axis.com>,
<pavel@ucw.cz>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH v3] stmmac: enable rx queues
Date: Thu, 22 Dec 2016 10:12:52 +0000 [thread overview]
Message-ID: <fb91a9e2-8387-f8be-db2f-2041a8152f2a@synopsys.com> (raw)
In-Reply-To: <20161221.132647.1022935257419607406.davem@davemloft.net>
Às 6:26 PM de 12/21/2016, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Tue, 20 Dec 2016 17:09:28 +0000
>
>> When the hardware is synthesized with multiple queues, all queues are
>> disabled for default. This patch adds the rx queues configuration.
>> This patch was successfully tested in a Synopsys QoS Reference design.
>>
>> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
>> ---
>> changes v2 -> v3 (Seraphin Bonnaffe):
>> - GMAC_RX_QUEUE_CLEAR macro simplified
>> changes v1 -> v2 (Niklas Cassel and Seraphin Bonnaffe):
>> - Instead of using number of DMA channels, lets use number of queues
>> - Create 2 flavors of RX queue enable Macros: AV and DCB (AV by default)
>> - Make sure that the RX queue related bits are cleared before setting
>> - Check if rx_queue_enable is available before executing
>
> This change seems more appropriate for net-next, please resubmit when
> that tree opens up again.
>
> Thanks.
>
Ok, great! Could you please send me an estimate of when the net-next is going to
open again?
Thanks
next prev parent reply other threads:[~2016-12-22 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 17:09 [PATCH v3] stmmac: enable rx queues Joao Pinto
2016-12-21 18:26 ` David Miller
2016-12-22 10:12 ` Joao Pinto [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-28 11:15 Joao Pinto
[not found] ` <CAJ3s=NB-ic4OrXPVPpYyoYrEwfwCmrAB8ZNPorpyU+5Do_b2=g@mail.gmail.com>
2016-12-28 11:53 ` Joao Pinto
2016-12-28 12:02 ` Kishan Sandeep
2016-12-28 12:05 ` Joao Pinto
[not found] ` <CAJ3s=NA0d=NAOPnWA2S9B_X2z9H6++wrH7nNyTv8Gbh_E_dmYg@mail.gmail.com>
[not found] ` <24c21cfd-87f5-2cae-6db1-32edc3333471@synopsys.com>
[not found] ` <389b0a01-1b17-c0f6-140f-bcd42c854480@synopsys.com>
[not found] ` <CAJ3s=NCs5j_iWkYTyNto6UaX-bmLjXVYu6DGKXQNfbafa5AVvg@mail.gmail.com>
2016-12-28 12:26 ` Joao Pinto
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=fb91a9e2-8387-f8be-db2f-2041a8152f2a@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=davem@davemloft.net \
--cc=hock.leong.kweh@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.cassel@axis.com \
--cc=pavel@ucw.cz \
--cc=peppe.cavallaro@st.com \
--cc=seraphin.bonnaffe@st.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).