From: "Måns Rullgård" <mans@mansr.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4] net: ethernet: add driver for Aurora VLSI NB8800 Ethernet controller
Date: Sat, 31 Oct 2015 18:44:02 +0000 [thread overview]
Message-ID: <yw1xd1vuc1zh.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <20151031180751.GA490@electric-eye.fr.zoreil.com> (Francois Romieu's message of "Sat, 31 Oct 2015 19:07:51 +0100")
Francois Romieu <romieu@fr.zoreil.com> writes:
> Måns Rullgård <mans@mansr.com> :
>> Francois Romieu <romieu@fr.zoreil.com> writes:
> [...]
>> > It looks like it receives, then tries to allocate new resources. If so
>> > it may deplete the ring and you should instead consider allocating new
>> > resources first, then receive data if alloc + map suceeded.
>>
>> The hardware receives a frame and stores it in the provided DMA buffer,
>> then raises an interrupt and moves on to the next buffer. When a buffer
>> is handed over to the network stack, a new one has to take its place in
>> the DMA queue. I'm not sure how you're suggesting this be done
>> differently.
>
> - The hardware raises an interrupt and moves on to the next packet
> - The driver allocates a new buffer - call it Bob - and maps it.
> - If it succeeds
> - The driver unmaps the received packet
> - The driver hands the received packet to the network stack
> - The driver hands Bob to the hardware
> - It it fails
> - The driver updates the dropped packet stats
> - The driver recycles the received - yet non-unmapped - packet to the
> hardware
Oh, I see. That's better.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2015-10-31 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 16:48 [PATCH v4] net: ethernet: add driver for Aurora VLSI NB8800 Ethernet controller Mans Rullgard
2015-10-30 22:28 ` Francois Romieu
2015-10-31 16:03 ` Måns Rullgård
2015-10-31 18:07 ` Francois Romieu
2015-10-31 18:44 ` Måns Rullgård [this message]
2015-10-31 17:21 ` Andy Shevchenko
2015-10-31 18:41 ` Måns Rullgård
2015-10-31 20:06 ` Andy Shevchenko
2015-10-31 21:41 ` Måns Rullgård
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=yw1xd1vuc1zh.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).