diff for duplicates of <2499748.LKgOIUjhgo@morokweng> diff --git a/a/1.txt b/N1/1.txt index 593bb63..f59357b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,42 +4,33 @@ Am Mittwoch, 1. Februar 2017, 16:37:58 BRST schrieb Michael Ellerman: > Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> writes: > > Paul Clarke [pc@us.ibm.com] wrote: > > --- -> >=20 +> > > > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001 ->=20 +> > I know it's been a while but I think it would still be good to get this > in a shape that we can merge it. -Sorry if this has been tried and didn't work or if I'm missing something=20 +Sorry if this has been tried and didn't work or if I'm missing something obvious: -Instead of this method of trying a small RMA size and rebooting to try a=20 -bigger size, could the "min RMA percentage of total RAM" field of the=20 +Instead of this method of trying a small RMA size and rebooting to try a +bigger size, could the "min RMA percentage of total RAM" field of the ibm_architecture_vec be used? -LoPAPR says that "The Initial size of the RMA is set to the greater of the= -=20 -values indicated by bytes 24-27 [min RMA] or 32 [min RMA percentage of tota= -l=20 -RAM] of option vector number 2 =E2=80=9COpen Firmware=E2=80=9D or minimum R= -MA size supported=20 -by the platform and capped by the maximum memory defined for the partition = -and=20 -the maximum size of the RMA supported by the platform. The respective selec= -ted=20 +LoPAPR says that "The Initial size of the RMA is set to the greater of the +values indicated by bytes 24-27 [min RMA] or 32 [min RMA percentage of total +RAM] of option vector number 2 “Open Firmware” or minimum RMA size supported +by the platform and capped by the maximum memory defined for the partition and +the maximum size of the RMA supported by the platform. The respective selected values are reported in the length of the first memory property." -My understanding is that these patches are intended for big guests with man= -y=20 -processors, but the RMA size isn't changed to 512MB outright because of=20 -worries that it could affect smaller guests. Since guests with many process= -ors=20 -tend to have more RAM as well, specifying a min RMA size of 256MB and a min= -=20 -RMA percentage of, say, 10% or 20% could make the host automatically alloca= -te=20 +My understanding is that these patches are intended for big guests with many +processors, but the RMA size isn't changed to 512MB outright because of +worries that it could affect smaller guests. Since guests with many processors +tend to have more RAM as well, specifying a min RMA size of 256MB and a min +RMA percentage of, say, 10% or 20% could make the host automatically allocate an adequate RMA size in the first boot. -=2D-=20 +-- Thiago Jung Bauermann IBM Linux Technology Center diff --git a/a/content_digest b/N1/content_digest index 6e4b70f..52b96aa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -17,44 +17,35 @@ "> Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> writes:\n" "> > Paul Clarke [pc@us.ibm.com] wrote:\n" "> > ---\n" - "> >=20\n" + "> > \n" "> > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001\n" - ">=20\n" + "> \n" "> I know it's been a while but I think it would still be good to get this\n" "> in a shape that we can merge it.\n" "\n" - "Sorry if this has been tried and didn't work or if I'm missing something=20\n" + "Sorry if this has been tried and didn't work or if I'm missing something \n" "obvious:\n" "\n" - "Instead of this method of trying a small RMA size and rebooting to try a=20\n" - "bigger size, could the \"min RMA percentage of total RAM\" field of the=20\n" + "Instead of this method of trying a small RMA size and rebooting to try a \n" + "bigger size, could the \"min RMA percentage of total RAM\" field of the \n" "ibm_architecture_vec be used?\n" "\n" - "LoPAPR says that \"The Initial size of the RMA is set to the greater of the=\n" - "=20\n" - "values indicated by bytes 24-27 [min RMA] or 32 [min RMA percentage of tota=\n" - "l=20\n" - "RAM] of option vector number 2 =E2=80=9COpen Firmware=E2=80=9D or minimum R=\n" - "MA size supported=20\n" - "by the platform and capped by the maximum memory defined for the partition =\n" - "and=20\n" - "the maximum size of the RMA supported by the platform. The respective selec=\n" - "ted=20\n" + "LoPAPR says that \"The Initial size of the RMA is set to the greater of the \n" + "values indicated by bytes 24-27 [min RMA] or 32 [min RMA percentage of total \n" + "RAM] of option vector number 2 \342\200\234Open Firmware\342\200\235 or minimum RMA size supported \n" + "by the platform and capped by the maximum memory defined for the partition and \n" + "the maximum size of the RMA supported by the platform. The respective selected \n" "values are reported in the length of the first memory property.\"\n" "\n" - "My understanding is that these patches are intended for big guests with man=\n" - "y=20\n" - "processors, but the RMA size isn't changed to 512MB outright because of=20\n" - "worries that it could affect smaller guests. Since guests with many process=\n" - "ors=20\n" - "tend to have more RAM as well, specifying a min RMA size of 256MB and a min=\n" - "=20\n" - "RMA percentage of, say, 10% or 20% could make the host automatically alloca=\n" - "te=20\n" + "My understanding is that these patches are intended for big guests with many \n" + "processors, but the RMA size isn't changed to 512MB outright because of \n" + "worries that it could affect smaller guests. Since guests with many processors \n" + "tend to have more RAM as well, specifying a min RMA size of 256MB and a min \n" + "RMA percentage of, say, 10% or 20% could make the host automatically allocate \n" "an adequate RMA size in the first boot.\n" "\n" - "=2D-=20\n" + "-- \n" "Thiago Jung Bauermann\n" IBM Linux Technology Center -342d1d64a19ef8f2af209f6f6441e3b124606647836ed0111e112f1e99eb6f3d +c6416483ba52d3032c98a7f11e074cccbf54c8193fe429e3cbd738cea3c11bce
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.