[Attention][FA3] Update FA3 to include new swizzle optimization

[LucasWilkinson]

vLLM side of vllm-project/flash-attention#82

meta-llama/Meta-Llama-3-8B-Instruct, 1xH100, 4k and 2k out

branch   rate     num_prompts  req/s    median TTFT (ms)   std TTFT     p99 TTFT     median TPOT (ms)   std TPOT     p99 TPOT    
------   ----     -----------  -----    ----------------   --------     --------     ----------------   --------     --------    
MAIN     1.00     120          0.88     141.95             29.83        287.21       11.07              0.84         11.67       
PR       1.00     120          0.89     137.69             28.51        277.24       10.81              0.84         11.40       
MAIN     2.00     240          1.53     177.97             54.18        415.02       25.73              4.63         30.20       
PR       2.00     240          1.54     176.99             52.59        403.90       25.72              4.60         30.08       
MAIN     3.00     360          1.65     361.44             18180.54     43681.80     42.99              8.20         52.66       
PR       3.00     360          1.66     345.31             17685.66     42551.03     42.69              8.00         52.07       
MAIN     4.00     480          1.66     54165.70           45848.99     119451.76    49.99              9.37         69.16       
PR       4.00     480          1.67     52780.84           45014.34     117440.91    49.40              9.16         68.40 

[gemini-code-assist]

Code Review

This pull request updates the flash-attention dependency to a new commit hash, likely to incorporate the 'FA3 swizzle optimization' mentioned in the PR title. While pinning to a commit is good for reproducibility, using a commit hash that is not part of a tag or a long-lived branch can pose a risk for future builds and maintenance. I've added a comment suggesting the use of a git tag for better long-term stability.

[gemini-code-assist]

Pinning dependencies to a specific commit hash is good for reproducibility. However, for long-term maintenance and release builds, it's better to use a git tag. Commit hashes that are not part of a branch or tag can be garbage collected by git, or become hard to track. Since this is a work-in-progress, it's acceptable for now, but it would be best to create a tag in the vllm-project/flash-attention repository for this commit before this PR is merged.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this pull request should remain open. Thank you!

[mergify]

Hi @LucasWilkinson, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[mergify]

Hi @LucasWilkinson, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @LucasWilkinson.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[mergify]

Documentation preview: https://vllm--23465.org.readthedocs.build/en/23465/