5 octa: Buy Profoto RFi Softbox Octa online

Processor part

Eight cores in Exynos 5 Octa, of course, are far from identical. Some even scolded Samsung for the deliberate «bulging» of this eight-core. That is, there are really eight cores, but in fact they are two different quad-core processors on one chip.

The first contains 4 ARM Cortex-A15 cores operating at a frequency of 0.2 to 1.8 GHz (in the Russian Galaxy S IV, the maximum frequency is limited to 1.6 GHz). Each core got 32 KB of L1 cache for instructions and 32 KB for data. There is also a general second-level cache — 2 MB — exclusively for data. In terms of area, this part of the chip occupies approximately 19mm ² .

Recall what an ARM Cortex-A15 is. The Cortex-A15 core boasts a 15-stage integer pipeline (the Cortex-A9 had only 8 stages). For floating point operations, the pipeline can be even longer, from 17 to 25 stages. ARM claims to have greatly improved the branch predictor, so a long pipeline should come in handy here.

The size of the reorder buffer has increased significantly. If the Cortex-A9 corecould store 32-40 decoded instructions in the buffer, then the Cortex-A15 — as many as 128. Instructions, as in the Cortex-A9, are executed out of order, but now this applies to any instructions, while the Cortex-A9 could process floating instructions comma and instructions from the NEON set only in order of priority.

ARM does not impose strict restrictions on chip manufacturing technology, so Cortex-A15 can be produced both in LP and Hpm (HKMG) processes — that is, using metal gates and dielectrics with a high dielectric constant. In the first case, the maximum core frequency does not exceed 1.5 GHz, in the second — 2.5. ARM carefully emphasizes that the Cortex-A15 supports large address spaces (LPAE), virtualization, and error correction codes.

Four Cortex-A15 cores are combined into one block with a 128-bit AMBA ACE bus, and the blocks, in turn, can also be combined using the high-speed CoreLink bus — there can be up to four blocks in one chip, that is, up to 16 cores. But back to our Exynos and the second block of processor cores in it.

The picture shows only a part of the chip

The second quad-core is built on more energy efficient ARM Cortex-A7 cores, with a frequency of 0.2 to 1.2 GHz. We briefly talked about the architecture of this type of cores in an article about Qualcomm SoCs. They have 32 KB L1 cache, and L2 cache is four times less: 512 KB for all four cores. At the same time, when viewed from the point of view of the area, this part is 5 times smaller: only 3.8 mm ² , and in terms of energy consumption — almost 6 times more economical.

Both processors are connected to a common universal interrupt controller and to a common data bus, through which they communicate with LPDDR3 memory. The memory bandwidth is quite impressive — 12.8 GB / s, exactly the same as the older Qualcomm Snapdragon 800 processor.

In both chips, the frequency and voltage of each core can be adjusted individually. In general, this whole design corresponds to the principles of the ARM big.LITTLE architecture — that is, Samsung did not invent this eight-wheeled bicycle, it was invented by ARM itself. Exynos 5 Octa is the first implementation of big.LITTLE in the industry.

How does it work?

In theory, most of the time the powerful Cortex-A15 cores are disabled and all tasks are handled by the economical Cortex-A7 cores. Samsung says the Cortex-A7 is great for «easy surfing the web», email and maps. The system sequentially connects more and more A7 cores as the load increases. Then the Cortex-A15 comes into play, which, according to the Koreans, do an excellent job with heavy games, but in fact they perform almost all tasks, with the exception of the three described above. Theoretically, it would be possible to use cores of different types in parallel, since the set of instructions in them is the same — ARM provided this option. But Samsung decided that this was not very beneficial in terms of energy saving, so at some point — while the power consumption is still within 1 W — the quad-core Cortex-A7 is turned off and all tasks are transferred to the Cortex-A15 cores, again thanks to the fact that A7 and A15 have a common set of instructions, and there are no problems during porting.

The moment when a switch is required is determined by the firmware from ARM. Switching between processors in theory should take no more than 20 microseconds. Further, all tasks are taken over by the A15 cores, and the more difficult the task is, the more cores will be involved. In this mode, the chip can consume up to 6 watts. Once the system has taken care of the hard work, the data will again be transferred to the A7 cores, and the A15 will fall asleep and stop eating electricity in four voracious throats.

Recall just in case: the specific performance of the Cortex-A7 core is about 1.9 DMIPS/MHz, and the Cortex-A15 core is about 3.5 DMIPS/MHz. If we take into account the difference in frequencies, then the maximum increase in performance when switching is obtained somewhere in 2.7 times. It should be noted that the increase in computing power correlates with the increase in energy consumption not as one to one. In order to get about a twofold increase in power when the A15 is turned on, the chip eats three times more energy than when running on the A7. No wonder ARM considers the Cortex-A7 architecture to be almost the most energy efficient! Another question is that you can get a performance increase and not twice, especially since the system never loads all the A7 cores to the maximum …

In conclusion of this part, we present a short video in which Samsung tried to explain how the processor part of Exynos 5 Octa is arranged.

Graphics

The PowerVR SGX544MP3 adapter is responsible for graphics in Exynos 5 Octa 5410. Recall that previous Exynos used ARM development graphics, that is, adapters called Mali, but something forced Samsung engineers to switch to using Imagination Technologies accelerators.

From the name of the chip — PowerVR SGX544MP3 — it is clear that this is a combination of three PowerVR SGX544. First, let’s recall what a single SGX544 is. Let’s start with the fact that shader processors are unified here (as in Adreno 320 and in all modern desktop video cards) — they are able to work with both vertex and pixel shaders. This allows you to fully load the graphics, regardless of what type of shaders prevails in the executable task. The SGX544 includes four USSE2 shader pipelines, each of which can execute four MAD operations per clock (multiply-add, an operation of the form a:=a+b*c). In total, one SGX544 performs 16 such operations per cycle.

It is logical to assume that the SGX544MP3 is capable of performing 48 MAD per clock. According to colleagues from Anandtech, Exynos 5 Octa graphics runs at 533 MHz. If we assume that one MAD operation is two floating point operations, then we get a peak performance of about 51.2 Gflops. For comparison: the graphic adapter GeForce 6800 Ultra could boast about the same performance. Now remember what TDP this adapter had. That’s the same.

In a single whole, three SGX544s are connected using a common bus, to which a common cache memory is connected. Most likely, you have never seen the mention of the SGX544 chip before, but the SGX543 came across for sure. It’s pretty much the same from an architectural point of view, except that the newer 544 fully supports DirectX 9.and Microsoft Shader Model 3.

Interesting: The SGX544MP3 belongs to Imagination Technologies’ GPU line called Series5XT. This is the last of the series launched into mass production, but not the newest series — the next versions of the iPad and iPhone will most likely use much more modern SGX600 adapters. Initially, the fifth family was supposed to be limited to working with Open GL ES 2. 0. However, Imagination realized that it was a bit of a delay with the development of the sixth series, and at the level of the driver development kit (DDK), they implemented a number of extensions from Open GL ES 3.0 in Series 5XT. It was not possible to fully add support for the third version of Open GL ES, but even so devices with PowerVR Series 5XT after updating the firmware will receive many previously inaccessible features that can make these accelerators faster and more modern.

By the way, for comparison: the Apple iPad with Retina Display, which we used to call iPad 3 for short, uses PowerVR SGX543MP4, that is, a slightly older, but a third thicker chip. The new iPad 4 has a much more productive SGX554MP4, so it’s definitely not worth considering the graphics in the Galaxy S4 close to the top of progress. True, the resolution of the iPads is much higher.

Others

The Exynos 5 Octa has an Image Signal Processor (ISP) built into the Exynos 5 Octa, allowing the camera to capture 13-megapixel images at 30 frames per second. Only Nikon 1 series cameras can compete in these indicators.

Multiformat Codec (MFC, Multiformat Codec) capable of playing video with a resolution of 1920×1080 at 60 frames per second in progressive scan. The maximum supported resolution of the built-in display is 2560×1600. Thanks to a fairly wide data bus, Exynos 5 Octa is theoretically capable of working with an external Full HD display over Wi-Fi.

Among other things, Exynos 5 Octa supports USB 3.0 and eMMC 5.0 standards. If you know everything about the first one even without us, then the latter limits the data transfer rate from the built-in drive at around 400 MB / s — and this is the level of the best modern SSDs, that is, the standard was developed with a large margin.

As far as we know, Exynos 5 Octa does not have a built-in cellular module. The fact that the Korean SGS4 with model number SHV-E300S has LTE, while the Russian GT-i9500 does not, is due only to the choice of modem.

Conclusion

So, Exynos 5 Octa (Exynos 5410) in theory promises to be a bit strange, but promising solution for powerful smartphones and tablets. If you try to compare this chip with something, then it would be logical to put it somewhere between the Snapdragon 600 and 800. graphics core.

We have already compared the performance of Exynos 5 Octa and Snapdragon 600 — the results of this comparison will be reported in the Samsung Galaxy S4 review, which will be released on 3DNews in the near future. In the same place, we will try to evaluate how efficiently the software switch between the quad-core parts of the chip works. How the Samsung eight-core will look against the background of the Snapdragon 800 — it will be possible to speak only when devices based on the latter appear at least on the horizon. But there is still NVIDIA Tegra 4…

Configuring Okta-Portal for ArcGIS | Documentation for ArcGIS Enterprise

You can set up Okta as an identity provider (IDP) for enterprise accounts in Portal for ArcGIS. The setup process consists of two main steps: registering your enterprise IDP with Portal for ArcGIS and registering Portal for ArcGIS with your enterprise IDP.

You can also enter metadata related to the corporate groups in your identity store into the portal. This will allow you to create groups in the portal that use existing enterprise groups from the identity store. When members sign in to the portal, access to resources, items, and data is secured by the rules defined in the corporate group. If you don’t provide the required enterprise group metadata, you can still create groups. However, membership rules will be determined by Portal for ArcGIS, not by the identity store.

Required information

Portal for ArcGIS must obtain certain attribute information from the IDP when a user logs in with a corporate account. The NameID attribute is required and must be sent by the IDP in response to a SAML request to integrate with Portal for ArcGIS. If an IDP user logs in, Portal for ArcGIS creates a new user named NameID in the user store. Valid characters for the value sent by the NameID attribute are letters, numbers, and _ (underscore). (dot) and @ (dog). Other characters will be replaced with an underscore in the username generated by Portal for ArcGIS.

Portal for ArcGIS supports the flow of givenName and email address attributes of a corporate account from a corporate IDP. When a user signs in with a corporate account and Portal for ArcGIS receives attributes named givenname and email or mail (either way), Portal for ArcGIS populates the full name and email address for the user account with the values ​​received from the IDP. We recommend specifying an email address from the corporate IDP so that the user can receive notifications.

Register Okta as an IDP in Portal for ArcGIS

1. Sign in to the portal website as your organization’s administrator and click My Organization > Edit Settings > Security.
2. In the Corporate Accounts via SAML section, click the Set Identity Provider button and enter the name of your organization (for example, City of Redlands) in the window that opens. When users sign in to the portal website, this text is displayed inside the SAML sign-in string (for example, Using a City of Redlands account).
3. Specify whether users can join the organization Automatically or After adding accounts to the portal. Selecting the first option allows users to sign in to the organization with a corporate account without administrator intervention. Their accounts are automatically registered with the organization the first time they sign in. In the second case, users will need to register the appropriate accounts in the organization, performed by the administrator through a special command line utility or Python script. Once the accounts are registered, users will be able to sign in to the organization.
4. Enter the metadata for the IDP using one of the options below:
   • File — Download or get a copy of the Okta metadata file and upload it to Portal for ArcGIS using the File option.

     If you are registering a service provider with Okta for the first time, you must obtain a metadata file after registering Portal for ArcGIS with Okta.

   • Options — Select this option if the metadata file is not available. Manually enter the values ​​and provide the requested parameters: login URL and certificate. Contact your Okta administrator for these values.
5. Advanced advanced options are available:
   • Encrypt claims — Select this option to encrypt Okta SAML assertion responses.
   • Enable Signed Request — Select this option to have Portal for ArcGIS sign the SAML authentication request that is sent to Okta.
   • Log out to Identity Provider — Select this option to have Portal for ArcGIS use the logout URL to log the user out of Okta. Enter the URL to use in the exit URL settings. If the IDP requires a logout URL to log in, you must enable the Enable Signed Request option.
   • Logout URL — The URL of the IDP used when the currently logged in user logs out.
   • Entity ID — Update this value to use the new entity ID to uniquely identify your Okta portal.

   The Encrypt Claims and Enable Signed Request settings use the samlcert certificate from the portal’s keystore. To use the new certificate, delete the samlcert certificate, create a new one with the same alias (samlcert) by following the steps in Importing the certificate into the portal, and restart the portal.

6. When finished, click Update Identity Provider.
7. Click the Get Service Provider button to download the portal metadata file. The information in this file will be used to register the portal as a trusted service provider with Okta.
9. You can also enter metadata related to the corporate groups in your identity store into the portal:
   1. Sign in to the ArcGIS Portal Directory as an administrator for your organization. The URL is https://webadaptorhost.domain.com/webadaptorname/portaladmin.
   2. Click Security > Configuration > Update Authentication Store.
   3. Place the JSON group configuration information in the Group Configuration Store (JSON format) text box.

      • If Windows Active Directory is used as the identity store, copy the following text and modify it to match your site settings:

         {
          "type": "WINDOWS",
          properties: {
            "isPasswordEncrypted": "false",
            "userPassword": "secret",
            "user": "mydomain\\winaccount"
          }
        } 

        In most cases, you will only need to change the values ​​for the user and userPassword parameters. Even though you enter the password in plain text, it will be encrypted when saved to the portal’s configuration directory and when viewed. The account you use for the user parameters only needs permission to view Windows group names on the network. If possible, use an account with a password that does not expire.

      • If you are using LDAP as the identity store, copy the following text and modify it to match your site settings:

         {
          "type": "LDAP", "properties": {
            "userPassword": "secret", "isPasswordEncrypted": "false", "user": "uid=admin,ou=system", "ldapURLForUsers": "ldaps://bar2:10636/ou=users,ou=ags ,dc=example,dc=com", "ldapURLForRoles": "ldaps://bar2:10636/dc=example,dc=com", "usernameAttribute": "cn", "caseSensitive": "false", "userSearchAttribute ": "cn", "memberAttributeInRoles": "member", "rolenameAttribute":"cn"
          }
        } 

        In most cases, you will only need to change the values ​​for the user, userPassword, ldapURLForUsers, and ldapURLForRoles parameters. The URL for your LDAP must be provided by the LDAP administrator.

        In the example above, the LDAP URL refers to users in a specific OU (ou=users). When users exist in multiple OUs, the LDAP URL can point to the higher level of the OU or even to the root level if necessary. In this case, the URL will look a little different:

        «ldapURLForUsers»: «ldaps://bar2:10636/dc=example,dc=com»,

        The account you use for user settings must have permission to view group names in your organization. Even though you enter the password in plain text, it will be encrypted when saved to the portal’s configuration directory and when viewed.

        If your LDAP is not case sensitive, set the caseSensitive parameter to false.

   4. After you have finished entering the JSON for your custom storage configuration, click Update Configuration to save your changes and restart the portal.

Register Portal for ArcGIS as a trusted service provider with Okta

1. Sign in to the Okta organization as an administrator member.
2. On the Applications tab, click the Add application button.
3. Click Create a new application and select the SAML 2.0 option. Click Create.
4. In General Settings, enter the Application name for your portal deployment and click Next.
5. On the SAML Configuration tab, do the following:
   1. Enter a value for SSO URL, for example, https://portalhostname.domain.com/portalcontext/sharing/rest/oauth3/saml/signin. This value can be copied from the service provider metadata file downloaded from your portal.
   2. Enter a value for the audience URL. By default, the value is set to portalhostname.domain.com.portalcontext. This value can be copied from the service provider metadata file downloaded from your portal.
   3. Leave Name ID Format set to Not Specified.