From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Wei Yang <weiyang@linux.vnet.ibm.com>,
gwshan@linux.vnet.ibm.com, mpe@ellerman.id.au,
benh@kernel.crashing.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V5 0/6] Redesign SR-IOV on PowerNV
Date: Thu, 3 Sep 2015 13:21:36 +1000 [thread overview]
Message-ID: <55E7BCC0.7010501@ozlabs.ru> (raw)
In-Reply-To: <1441243792-2074-1-git-send-email-weiyang@linux.vnet.ibm.com>
On 09/03/2015 11:29 AM, Wei Yang wrote:
> In original design, it tries to group VFs to enable more number of VFs in the
> system, when VF BAR is bigger than 64MB. This design has a flaw in which one
> error on a VF will interfere other VFs in the same group.
>
> This patch series change this design by using M64 BAR in Single PE mode to
> cover only one VF BAR. By doing so, it gives absolute isolation between VFs.
>
> v5:
> * rebase on top of v4.2, with commit 68230242cdb "net/mlx4_core: Add port
> attribute when tracking counters" reverted
> * test ssh from guest to host via VF passed and then shutdown the guest
> * no code change
This is weak test actually. When I try to load it more (described in
another mail thread with the "mlx4" subject, please respond there), the
host is crashing quite soon.
> v4:
> * rebase the code on top of v4.2-rc7
> * switch back to use the dynamic version of pe_num_map and m64_map
> * split the memory allocation and PE assignment of pe_num_map to make it
> more easy to read
> * check pe_num_map value before free PE.
> * add the rename reason for pe_num_map and m64_map in change log
> v3:
> * return -ENOSPC when a VF has non-64bit prefetchable BAR
> * rename offset to pe_num_map and define it staticly
> * change commit log based on comments
> * define m64_map staticly
> v2:
> * clean up iov bar alignment calculation
> * change m64s to m64_bars
> * add a field to represent M64 Single PE mode will be used
> * change m64_wins to m64_map
> * calculate the gate instead of hard coded
> * dynamically allocate m64_map
> * dynamically allocate PE#
> * add a case to calculate iov bar alignment when M64 Single PE is used
> * when M64 Single PE is used, compare num_vfs with M64 BAR available number
> in system at first
>
> Wei Yang (6):
> powerpc/powernv: don't enable SRIOV when VF BAR has non
> 64bit-prefetchable BAR
> powerpc/powernv: simplify the calculation of iov resource alignment
> powerpc/powernv: use one M64 BAR in Single PE mode for one VF BAR
> powerpc/powernv: replace the hard coded boundary with gate
> powerpc/powernv: boundary the total VF BAR size instead of the
> individual one
> powerpc/powernv: allocate sparse PE# when using M64 BAR in Single PE
> mode
>
> arch/powerpc/include/asm/pci-bridge.h | 7 +-
> arch/powerpc/platforms/powernv/pci-ioda.c | 328 ++++++++++++++++--------------
> 2 files changed, 175 insertions(+), 160 deletions(-)
>
--
Alexey
next prev parent reply other threads:[~2015-09-03 3:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 1:29 [PATCH V5 0/6] Redesign SR-IOV on PowerNV Wei Yang
2015-09-03 1:29 ` [PATCH V5 1/6] powerpc/powernv: don't enable SRIOV when VF BAR has non 64bit-prefetchable BAR Wei Yang
2015-09-03 1:29 ` [PATCH V5 2/6] powerpc/powernv: simplify the calculation of iov resource alignment Wei Yang
2015-09-03 1:29 ` [PATCH V5 3/6] powerpc/powernv: use one M64 BAR in Single PE mode for one VF BAR Wei Yang
2015-09-03 1:29 ` [PATCH V5 4/6] powerpc/powernv: replace the hard coded boundary with gate Wei Yang
2015-09-03 1:29 ` [PATCH V5 5/6] powerpc/powernv: boundary the total VF BAR size instead of the individual one Wei Yang
2015-09-03 1:29 ` [PATCH V5 6/6] powerpc/powernv: allocate sparse PE# when using M64 BAR in Single PE mode Wei Yang
2015-09-03 3:21 ` Alexey Kardashevskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 2:46 [PATCH V5 0/6] Redesign SR-IOV on PowerNV Wei Yang
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=55E7BCC0.7010501@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=weiyang@linux.vnet.ibm.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).