1. 24 1月, 2014 14 次提交
  2. 22 1月, 2014 2 次提交
    • J
      mm: add overcommit_kbytes sysctl variable · 49f0ce5f
      Jerome Marchand 提交于
      Some applications that run on HPC clusters are designed around the
      availability of RAM and the overcommit ratio is fine tuned to get the
      maximum usage of memory without swapping.  With growing memory, the
      1%-of-all-RAM grain provided by overcommit_ratio has become too coarse
      for these workload (on a 2TB machine it represents no less than 20GB).
      
      This patch adds the new overcommit_kbytes sysctl variable that allow a
      much finer grain.
      
      [akpm@linux-foundation.org: coding-style fixes]
      [akpm@linux-foundation.org: fix nommu build]
      Signed-off-by: NJerome Marchand <jmarchan@redhat.com>
      Cc: Dave Hansen <dave.hansen@linux.intel.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      49f0ce5f
    • R
      /proc/meminfo: provide estimated available memory · 34e431b0
      Rik van Riel 提交于
      Many load balancing and workload placing programs check /proc/meminfo to
      estimate how much free memory is available.  They generally do this by
      adding up "free" and "cached", which was fine ten years ago, but is
      pretty much guaranteed to be wrong today.
      
      It is wrong because Cached includes memory that is not freeable as page
      cache, for example shared memory segments, tmpfs, and ramfs, and it does
      not include reclaimable slab memory, which can take up a large fraction
      of system memory on mostly idle systems with lots of files.
      
      Currently, the amount of memory that is available for a new workload,
      without pushing the system into swap, can be estimated from MemFree,
      Active(file), Inactive(file), and SReclaimable, as well as the "low"
      watermarks from /proc/zoneinfo.
      
      However, this may change in the future, and user space really should not
      be expected to know kernel internals to come up with an estimate for the
      amount of free memory.
      
      It is more convenient to provide such an estimate in /proc/meminfo.  If
      things change in the future, we only have to change it in one place.
      Signed-off-by: NRik van Riel <riel@redhat.com>
      Reported-by: NErik Mouw <erik.mouw_2@nxp.com>
      Acked-by: NJohannes Weiner <hannes@cmpxchg.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      34e431b0
  3. 21 1月, 2014 3 次提交
  4. 17 1月, 2014 2 次提交
    • L
      gpio: mcp23s08: Add irq functionality for i2c chips · 4e47f91b
      Lars Poeschel 提交于
      This adds interrupt functionality for i2c chips to the driver.
      They can act as a interrupt-controller and generate interrupts, if
      the inputs change.
      This is tested with a mcp23017 chip on an arm based platform.
      
      v3:
      - be a bit more clear that the irq functionality is also available
        on spi versions of the chips, but the linux driver does not support
        this yet
      
      v2:
      - some more word about irq-mirror property in binding doc
      - use of_read_bool instead of of_find_property for
        "interrupt-contrller" and "irq-mirror"
      - cache the "interrupt-controller" for remove function
      - do set the irq-mirror bit only if device is marked as
        interrupt-controller
      - do create the irq mapping and setup of irq_desc of all possible
        interrupts in probe path instead of in gpio_to_irq
      - mark gpios as in use as interrupts in irq in irq_startup and
        unlock it in irq_shutdown
      - rename virq to child_irq
      - remove dev argument from mcp23s08_irq_setup function
      - move gpiochip_add before mcp23s08_irq_setup in probe path
      Signed-off-by: NLars Poeschel <poeschel@lemonage.de>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      4e47f91b
    • M
      dm cache: add policy name to status output · 2e68c4e6
      Mike Snitzer 提交于
      The cache's policy may have been established using the "default" alias,
      which is currently the "mq" policy but the default policy may change in
      the future.  It is useful to know exactly which policy is being used.
      
      Add a 'real' member to the dm_cache_policy_type structure and have the
      "default" dm_cache_policy_type point to the real "mq"
      dm_cache_policy_type.  Update dm_cache_policy_get_name() to check if
      real is set, if so report the name of the real policy (not the alias).
      Requested-by: NJonathan Brassow <jbrassow@redhat.com>
      Signed-off-by: NMike Snitzer <snitzer@redhat.com>
      2e68c4e6
  5. 16 1月, 2014 2 次提交
    • S
      pinctrl: Add pinctrl binding for Broadcom Capri SoCs · 9bb412e5
      Sherman Yin 提交于
      Adds pinctrl driver devicetree binding for Broadcom Capri (BCM281xx) SoCs.
      
      v4: Changed valid values for "bias-pull-up" property for I2C pins.
          Expanded pin configuration node example.
      v3: Use generic pin config properties instead of brcm-specific ones.
          Clarified pin types (standard, i2c, hdmi).
      v2: Use hyphens instead of underscore in DT property names.
      
      Device tree bindings maintainers ECG:
                 _             _          _        _        _
      __________/ \   ________/ \   _____/ \   ___/ \   ___/ \   __
                   \_/           \_/        \_/      \_/      \_/
      Signed-off-by: NSherman Yin <syin@broadcom.com>
      Reviewed-by: NChristian Daudt <bcm@fixthebug.org>
      Reviewed-by: NMatt Porter <matt.porter@linaro.org>
      Acked-by: NMark Rutland <mark.rutland@arm.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      9bb412e5
    • H
      x86, apic, kexec: Add disable_cpu_apicid kernel parameter · 151e0c7d
      HATAYAMA Daisuke 提交于
      Add disable_cpu_apicid kernel parameter. To use this kernel parameter,
      specify an initial APIC ID of the corresponding CPU you want to
      disable.
      
      This is mostly used for the kdump 2nd kernel to disable BSP to wake up
      multiple CPUs without causing system reset or hang due to sending INIT
      from AP to BSP.
      
      Kdump users first figure out initial APIC ID of the BSP, CPU0 in the
      1st kernel, for example from /proc/cpuinfo and then set up this kernel
      parameter for the 2nd kernel using the obtained APIC ID.
      
      However, doing this procedure at each boot time manually is awkward,
      which should be automatically done by user-land service scripts, for
      example, kexec-tools on fedora/RHEL distributions.
      
      This design is more flexible than disabling BSP in kernel boot time
      automatically in that in kernel boot time we have no choice but
      referring to ACPI/MP table to obtain initial APIC ID for BSP, meaning
      that the method is not applicable to the systems without such BIOS
      tables.
      
      One assumption behind this design is that users get initial APIC ID of
      the BSP in still healthy state and so BSP is uniquely kept in
      CPU0. Thus, through the kernel parameter, only one initial APIC ID can
      be specified.
      
      In a comparison with disabled_cpu_apicid, we use read_apic_id(), not
      boot_cpu_physical_apicid, because on some platforms, the variable is
      modified to the apicid reported as BSP through MP table and this
      function is executed with the temporarily modified
      boot_cpu_physical_apicid. As a result, disabled_cpu_apicid kernel
      parameter doesn't work well for apicids of APs.
      
      Fixing the wrong handling of boot_cpu_physical_apicid requires some
      reviews and tests beyond some platforms and it could take some
      time. The fix here is a kind of workaround to focus on the main topic
      of this patch.
      Signed-off-by: NHATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
      Link: http://lkml.kernel.org/r/20140115064458.1545.38775.stgit@localhost6.localdomain6Signed-off-by: NH. Peter Anvin <hpa@zytor.com>
      151e0c7d
  6. 15 1月, 2014 3 次提交
  7. 14 1月, 2014 1 次提交
  8. 13 1月, 2014 1 次提交
  9. 12 1月, 2014 1 次提交
  10. 11 1月, 2014 1 次提交
  11. 10 1月, 2014 5 次提交
  12. 09 1月, 2014 5 次提交