From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, Amir Vadai <amirv@mellanox.com>
Subject: Re: [PATCH net-next] net/mlx4: use one page fragment per incoming frame
Date: Mon, 03 Jun 2013 11:24:48 -0700 [thread overview]
Message-ID: <51ACDF70.4050301@hp.com> (raw)
In-Reply-To: <1370283150.24311.179.camel@edumazet-glaptop>
On 06/03/2013 11:12 AM, Eric Dumazet wrote:
> On Mon, 2013-06-03 at 11:05 -0700, Rick Jones wrote:
>
>> I take it this is a > 10 Gbit/s NIC?
>>
>
> Well, I guess so !
>
> Or something is really strange with this NIC !
Indeed.
>> What if any is the downside to an incoming stream of small packets?
>
> These kind of NIC are aimed for performance, I was told.
>
> 1) It would be strange to use them on memory constrained machines.
>
> 2) using 1536 bytes fragments is better than most other NIC drivers, as
> they usually use 2048 or 4096 bytes frags
>
> 3) Current memory allocations done in mlx4 uses order-2 pages, and
> nobody yet complained that these allocation might fail...
I was thinking more about getting up to a socket and finding
insufficient overhead remaining to hold the packet.
rick
next prev parent reply other threads:[~2013-06-03 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 17:54 [PATCH net-next] net/mlx4: use one page fragment per incoming frame Eric Dumazet
2013-06-03 18:05 ` Rick Jones
2013-06-03 18:12 ` Eric Dumazet
2013-06-03 18:24 ` Rick Jones [this message]
2013-06-03 18:26 ` Eric Dumazet
2013-06-04 8:40 ` Amir Vadai
2013-06-05 0:28 ` David Miller
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=51ACDF70.4050301@hp.com \
--to=rick.jones2@hp.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).