From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: David.Laight@ACULAB.COM, rick.jones2@hp.com,
cascardo@linux.vnet.ibm.com, netdev@vger.kernel.org,
yevgenyp@mellanox.co.il, ogerlitz@mellanox.com,
amirv@mellanox.com, brking@linux.vnet.ibm.com,
leitao@linux.vnet.ibm.com, klebers@linux.vnet.ibm.com
Subject: Re: [PATCH] mlx4_en: map entire pages to increase throughput
Date: Tue, 17 Jul 2012 15:50:59 +0200 [thread overview]
Message-ID: <1342533059.2626.661.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120717.055005.1912765690890797652.davem@davemloft.net>
On Tue, 2012-07-17 at 05:50 -0700, David Miller wrote:
> From: "David Laight" <David.Laight@ACULAB.COM>
> Date: Tue, 17 Jul 2012 13:42:04 +0100
>
> > Would there be any mileage in permanently allocating IOMMU
> > virtual address to the ring entries, then 'just' assigning
> > the correct physical address during rx/tx setup?
>
> There is a not a one to one mapping between these two entities,
> in particular on the transmit side.
>
> A transmit packet can have multiple segments, some of which are
> larger than one IOMMU page.
And on rx side, permanently allocating IOMMU would need to copy all
incoming frames to newly allocated memory.
Annot this IOMMU performance problem can be solved on its side,
instead of having to shuffle things in all drivers ?
next prev parent reply other threads:[~2012-07-17 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 17:01 [PATCH] mlx4_en: map entire pages to increase throughput Thadeu Lima de Souza Cascardo
2012-07-16 17:27 ` Rick Jones
2012-07-16 19:06 ` Thadeu Lima de Souza Cascardo
2012-07-16 19:42 ` Rick Jones
2012-07-16 20:36 ` Or Gerlitz
2012-07-16 20:43 ` Or Gerlitz
2012-07-16 20:57 ` Thadeu Lima de Souza Cascardo
2012-07-18 14:59 ` Or Gerlitz
2012-07-16 20:47 ` Thadeu Lima de Souza Cascardo
2012-07-16 21:08 ` Rick Jones
2012-07-17 5:29 ` David Miller
2012-07-17 12:42 ` David Laight
2012-07-17 12:50 ` David Miller
2012-07-17 13:36 ` David Laight
2012-07-17 13:46 ` David Miller
2012-07-17 13:50 ` Eric Dumazet [this message]
2012-07-17 18:17 ` Rick Jones
2012-07-17 20:10 ` Brian King
2012-07-17 20:20 ` David Miller
2012-07-19 17:53 ` 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=1342533059.2626.661.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=amirv@mellanox.com \
--cc=brking@linux.vnet.ibm.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=klebers@linux.vnet.ibm.com \
--cc=leitao@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=rick.jones2@hp.com \
--cc=yevgenyp@mellanox.co.il \
/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