On Tue, 2015-11-10 at 17:12 +1100, Gavin Shan wrote:
>
> > So we require the interface to be opened to talk, so far so good,
> > the NC-SI stack doesn't even need to open it itself, it's acceptable
> > to require userspace to do it. IE. Userspace will chose what interface
> > to use, open it (for
On Tue, Nov 10, 2015 at 07:28:24AM +1100, Benjamin Herrenschmidt wrote:
>On Mon, 2015-11-09 at 18:30 +1100, Gavin Shan wrote:
>>
>> Yeah, It's something that I hilighed in the cover letter. I was
>> thinking we might need a better way to enable Tx/Rx before the
>> interrupt is up, but couldn't fig
On Mon, 2015-11-09 at 18:30 +1100, Gavin Shan wrote:
>
> Yeah, It's something that I hilighed in the cover letter. I was
> thinking we might need a better way to enable Tx/Rx before the
> interrupt is up, but couldn't figure out one way. So I need some
> advice here.
No, that's not right. For Tx/
On Mon, Nov 09, 2015 at 11:32:07AM +1100, Benjamin Herrenschmidt wrote:
>On Mon, 2015-11-09 at 11:10 +1100, Gavin Shan wrote:
>>
>> -if (likely(netif_running(netdev))) {
>> +/* When running in NCSI mode, the interface should be
>> + * ready to receive or transmit NCSI packet before it'
On Mon, 2015-11-09 at 11:10 +1100, Gavin Shan wrote:
>
> - if (likely(netif_running(netdev))) {
> + /* When running in NCSI mode, the interface should be
> + * ready to receive or transmit NCSI packet before it's
> + * opened.
> + */
No, that's not right. open/close is when
The NIC has the possibility to connect to NCSI package and channel.
This supports NCSI enabled interface. When the network device is
registered, the accompanying NCSI device is registered. When the
interface is to be brought up, the NCSI device is started to probe
NCSI topology and choose one activ
