iscsi bidi & varlen support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Pete Wyckoff |
|---|---|
| Series | R-b R-b R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3 ver2] iscsi bidi & varlen support
Quoted 26 lines · Boaz Harrosh
Cheers after 1.3 years these can go in.
[PATCH 1/3] iscsi: extended cdb support
The varlen support is not yet in mainline for
block and scsi-ml. But the API for drivers will not change. All LLD need to do ismax_commandto the it's maximum and be ready for bigger commands. This is what's done here. Once these commands start coming iscsi will be ready for them.[PATCH 2/3] iscsi: bidi support - libiscsi [PATCH 3/3] iscsi: bidi support -
iscsi_tcp
bidirectional commands support in iscsi. iSER is not yet ready, but it will not break. There is already a mechanism in libiscsi that will return error if bidi commands are sent iSER way.Pete please send me the iSER bits so we can port them to this latest version.
Mike these patches are ontop of iscs branch of the iscsi git tree, they will apply but for compilation you will need to sync with Linus mainline. The patches are for the in-tree iscsi code. I own you the compat patch for the out-off-tree code, but this I will only be Sunday.
Quoted 8 lines
If we do it fast it might get accepted to 2.6.25 merge window
Everybody is invited to a party at Shila ben-yhuda 52 Tel-Aviv 9:45 pm. Drinks and wonderful see-food on us :)
Boaz
-
Everything the same as before. But working this time. Also Pete's comment about second patch, was correct and code is now fixed.
I have got Mike's Signed-off-by, on these they were tested and approved by him. So they are for scsi-misc. But ... James? is there any chance these can go into scsi-rc-fixes for the 2.6.25 kernel? The reason they are so late was mainly because of a fallout in the merge process and a bug that was introduced because of that, but they were intended to go together with bidi into 2.6.25. Also as an important client code to the bidi-api that is introduced in 2.6.25 kernel.
Thanks
Boaz