In RAID0 take a stripe size of 64k Is stripe size the amount placed on each disk?
Disk A 64k (stripe size is 64k)
Disk B 64korIs the stripe size the total size of the block that is fed to the set of disks?
Disk A 32k (stripe size is 64k)
Disk B 32k

The RAID hardware/software is Intel chipset SATA controller, the OS is Windows.

Lets visit the people who should know

1) microsoft
The stripe size is the per disk unit of data distribution within a
RAID set. Stripe size is also referred to as block size.

2) Intel forum
. . . If you have a 32KB cluster. Let's say you have a 64KB strip size on
RAID controller, and let's assume it's a sequential write. The first
file will be written on the first 32KB of the strip on the first disk.
Then the first 32KB of the 2nd file will be written to the rest 32KB
of the strip on the first disk.

Terminology used when discussing Data Striping

Stripe/Block:

A stripe is the smallest chunk of data within a RAID array that can be addressed, in the diagram above the size of A1 would be considered the Stripe size this size can range from on 4-256KB (These are not hard limits, just common application)

Stripe-Width:

Stripe-width is the measurement of the number of drives in a data striping array in the above this would - Stripe-Width = 2

If we were to add 2 more drives to our array it would result in - Stripe-Width = 4

Logical Drive:

Your logical drive is the combined value of all stripes.

Stripe-Size:

Now this from the research I have done is a very ambiguous term. However for Intel Southbridges ICH7R, ICH8R and ICH9R this referees to a single stripe or a single drive

Now as you can tell from your own research some people will will use Stripe-Size to refer to the Size of a Stripe where others will refer to it as the size of a Stripe times the Strip-width

Their is a lot of misuse of language used all across the internet as their is no central control for it Language; due to the face their are so many variants for data striping registered it's unlikely without a central control we will get this defined

Simple thought: Imagine a RAID 0 with three member disks (which is a totally valid setup). If the stripe size would be the total size of the block that is fed to the set of disks, with a stripe size of 64 KiB, every disk would need to write 21845.33 bytes, which is not possible at all.

I believe that there is no conflict between the two sources you quoted,
because the strip-size is not the same as the sector-size.

Sector-size is known to the operating-system, and the sector is the smallest unit that can be allocated on the disk for one file.

Strip-size is known to the RAID controller and is the smallest unit that can be
read/written in one read/write operation.

Therefore if the strip-size is 64K and the sector-size is 32K,
then there are two sectors in each strip and the operating system may allocate each of the two sectors to two different files, letting the RAID controller take care of the details.

So the answer is that strip-size of 64K is 64K on each of the disks.
As a conclusion, strip-size should equal sector-size when the files are relatively small.
A large strip-size is more efficient only for large files and for sequential
read/write operations or the random access of large chunks.

Agreed. The second source is stating that for a 64KB strip size, for that particular example, 32KB (the whole first file) + 32KB (32KB of 96KB of the second file) is written to the first disk and 64KB (the remaining 64KB of the 96KB second file) is written to the second disk. So a total of 128KB is written across 2 disks with 64KB written to each disk giving the 64KB strip size.
–
SLaGSep 19 '13 at 6:55