Bug 1470027 - just a test !Dont worry!
just a test !Dont worry!
Product: Extended Engineering Testing
Classification: Red Hat
Component: Limits-Testing (Show other bugs)
All NetBSD
unspecified Severity urgent
: ---
: ---
Assigned To: kernel-general-test-team@redhat.com
Depends On:
  Show dependency treegraph
Reported: 2017-07-12 05:52 EDT by zhao chuanrui
Modified: 2017-07-13 07:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-13 07:48:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description zhao chuanrui 2017-07-12 05:52:38 EDT
System Under Test "SUT" Hardware Description:
1. Brief description of hardware
A) SUT Info:
   system name=
B) CPU Info:
   model name=
   total cpu count=
C) Memory Info:
   dimm part#'s=
   memory amount=

2. Link to the Hardware Certifications for existing system
A) Base Certification
B) Supplemental Certification

3. List known issues
A) Existing BZ's
B) Existing Hardware Errata
C) Existing KBase articles

4. Memory specifications
Please provide a brief description for the following:
A) What is the expected bandwidth of the memory subsystem system wide?
   (If we run many instances of memory intensive applications where
   each application does not cross NUMA boundaries, how much
   aggregate bandwidth might we expect on the server?)
B) Does the memory subsystem support NORMAL -vs- PERFORMANCE
   mode at the management/BIOS layer? If so what is it set to?
C) How many memory channels per socket for specific CPU?
D) How many channels per socket are actually populated on the SUT?

Note You need to log in before you can comment on or make changes to this bug.