From: robert.jarzmik@free.fr
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] net: smc1111: fix memory congestions
Date: Mon, 5 Jan 2015 17:16:48 +0100 (CET) [thread overview]
Message-ID: <1822252708.362857815.1420474608722.JavaMail.root@zimbra1-e1.priv.proxad.net> (raw)
In-Reply-To: <20150105121150.GC4544@pengutronix.de>
----- Mail original -----
De: "Sascha Hauer" <s.hauer@pengutronix.de>
À: "Robert Jarzmik" <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Envoyé: Lundi 5 Janvier 2015 13:11:50
Objet: Re: [PATCH] net: smc1111: fix memory congestions
> I don't know the hardware (not anymore, fortunately ;), but isn't it
> possible to dedicate one bucket for transmitting only, so that it will
> never be occupied by a received packet?
None I'm aware of.
I've been through the specification many times, and my understanding is
that :
- the MMU allocation is symmetric (either from CPU for TX or from NIC
for RX)
- there is no configurable threshold or limit
- first customer is first served from the MMU point of view
Cheers.
--
Robert
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-05 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 20:04 [PATCH] commands: loady: fix bug with netconsole Robert Jarzmik
2015-01-01 20:04 ` [PATCH] net: smc1111: fix memory congestions Robert Jarzmik
2015-01-05 12:11 ` Sascha Hauer
2015-01-05 16:16 ` robert.jarzmik [this message]
2015-01-06 13:58 ` Sascha Hauer
2015-01-01 20:04 ` [PATCH] net: smc1111: move print_packet function Robert Jarzmik
2015-01-05 12:12 ` Sascha Hauer
2015-01-05 12:12 ` [PATCH] commands: loady: fix bug with netconsole Sascha Hauer
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=1822252708.362857815.1420474608722.JavaMail.root@zimbra1-e1.priv.proxad.net \
--to=robert.jarzmik@free.fr \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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