Christoph Hellwig, mir\u00ebmbajt\u00ebsi i n\u00ebn-sistemit DMA, KVM, Slab Allocator dhe arkitektur\u00ebs PowerPC n\u00eb b\u00ebrtham\u00ebn Linux, i cili dikur ka qen\u00eb an\u00ebtar i komitetit teknik t\u00eb organizat\u00ebs Linux Foundation dhe ka qen\u00eb padit\u00ebs n\u00eb nj\u00eb proces gjyq\u00ebsor n\u00eb lidhje me GPL kund\u00ebr VMware, refuzoi t\u00eb konfirmoj\u00eb patch-et lidhur me mb\u00ebshtetje p\u00ebr zhvillimin e driverrave n\u00eb gjuh\u00ebn Rust. Patch-et e propozuara shtonin lidhje mbi disa funksione t\u00eb n\u00ebn-sistemit DMA, duke lejuar p\u00ebrdorimin e DMA n\u00eb driverrat n\u00eb gjuh\u00ebn Rust. <\/p>\n
Si arsye p\u00ebr refuzimin u p\u00ebrmend komplifikimi i mb\u00ebshtetjes s\u00eb kodit n\u00eb prani t\u00eb lidhjeve n\u00eb gjuh\u00eb t\u00eb tjera dhe d\u00ebshira p\u00ebr t\u00eb ruajtur nd\u00ebrfaqet programore p\u00ebr DMA n\u00eb nj\u00eb form\u00eb t\u00eb lexueshme n\u00eb gjuh\u00ebn C, pa e shpjeguar n\u00eb m\u00ebnyr\u00eb t\u00eb paqart\u00eb p\u00ebrmes lidhjeve t\u00eb panjohura. Christoph sugjeroi q\u00eb t\u00eb drejtoheshin drejtp\u00ebrdrejt n\u00eb API-n\u00eb origjinale C t\u00eb DMA n\u00eb \u00e7do driver n\u00eb gjuh\u00ebn Rust, p\u00ebr t\u00eb mos krijuar abstraksione shtes\u00eb, mbi t\u00eb cilat do t\u00eb detyroheshin t\u00eb varen ata q\u00eb mb\u00ebshtesin kernelin. <\/p>\n
Zhvilluesit e patch-eve kan\u00eb treguar se do t\u00eb marrin p\u00ebrsip\u00ebr t\u00ebr\u00eb pun\u00ebn p\u00ebr mb\u00ebshtetjen e kodit n\u00eb Rust, jan\u00eb t\u00eb gatsh\u00ebm t\u00eb mb\u00ebshtesin k\u00ebto patch-e vet\u00eb dhe e kan\u00eb nxjerr\u00eb mb\u00ebshtetje n\u00eb nj\u00eb n\u00ebn-katalog t\u00eb ve\u00e7ant\u00eb (rust\/kernel\/dma.rs). N\u00eb p\u00ebrgjigje, Kristof vendosi nj\u00eb veto (\u00e2\u20ac\u0153Nacked-by\u00e2\u20ac) p\u00ebr pranimin e patch-eve t\u00eb lidhura me Rust dhe tha se nuk kishte nevoj\u00eb p\u00ebr nj\u00eb mb\u00ebshtet\u00ebs tjet\u00ebr. Kristof shpalli se n\u00ebse zhvilluesit e mb\u00ebshtetjes d\u00ebshirojn\u00eb t\u00eb arrijn\u00eb pamund\u00ebsin\u00eb e mb\u00ebshtetjes s\u00eb Linux-it p\u00ebr shkak t\u00eb p\u00ebrzierjes s\u00eb disa gjuh\u00ebve n\u00eb nj\u00eb baz\u00eb kodi, ata duhet ta b\u00ebjn\u00eb k\u00ebt\u00eb n\u00eb pajisjen e tyre dhe jo ta p\u00ebrhapin k\u00ebt\u00eb tumor n\u00eb sistemet kryesore t\u00eb b\u00ebrtham\u00ebs. <\/p>\n
Megjithat\u00eb, Christoph sqaroi se nuk ka asgj\u00eb kund\u00ebr gjuh\u00ebs Rust dhe e konsideron at\u00eb nj\u00eb nga gjuh\u00ebt m\u00eb t\u00eb mira t\u00eb reja, por \u00ebsht\u00eb kund\u00ebr p\u00ebrzierjes s\u00eb kodit n\u00eb gjuh\u00eb t\u00eb ndryshme. Sipas Christoph, ai \u00ebsht\u00eb p\u00ebr krijimin e projekteve t\u00eb reja n\u00eb Rust, por \u00ebsht\u00eb kund\u00ebr p\u00ebrzierjes s\u00eb Rust n\u00eb bazat e m\u00ebdha t\u00eb kodit n\u00eb C, pasi kjo p\u00ebrzierje zvog\u00eblon ndjesh\u00ebm leht\u00ebsin\u00eb e mb\u00ebshtetjes s\u00eb kernelit si nj\u00eb projekt i integruar. <\/p>\n
The essence of the problems with support lies in the fact that Rust bindings make maintainers dependent on the code written in Rust. At first glance, it seems that bindings are merely layers over C structures and functions, which do not affect the development and support of C code. However, this is not the case. With such bindings in place, developers of subsystems written in C must consider the impact of their changes on the continued functionality of the bindings. Any change in data structures or internal functions in C can lead to a need for changes in the bindings code, so changes affecting bindings in C code need to be monitored and synchronized with the Rust code. Many maintainers are not ready to take on the additional responsibility for fixing issues arising in Rust code and are unwilling to spend their time tracking the state of Rust bindings. <\/p>\n
The situation with the complexity of support is not theoretical. Jason Gunthorpe, maintainer of TPM, VFIO, and Infiniband at NVIDIA, joined the discussion and provided an example where Linus Torvalds rejected a pull request with changes in the memory management subsystem, as this change led to a failure when attempting to build the kernel with Rust support enabled. The failure occurred because the maintainers of the Rust code did not add the necessary changes to the bindings generator (bindgen). Thus, the maintainers of the memory management subsystem, while advancing a change that was completely correct from the perspective of C code and the kernel as a whole, found themselves dependent on optional third-party code in the kernel, for which other people are responsible. <\/p>\n
Refuzimi p\u00ebr t\u00eb pranuar kodin e mb\u00ebshtetjes mbi thirrjet DMA e vendosi projektin Rust p\u00ebr Linux n\u00eb nj\u00eb ng\u00ebr\u00e7, pasi pa k\u00ebto mb\u00ebshtetje zhvillimi i driver-ave t\u00eb plota n\u00eb gjuh\u00ebn Rust do t\u00eb b\u00ebhej i v\u00ebshtir\u00eb. Hektor Martin, mbajt\u00ebsi i kodit p\u00ebr mb\u00ebshtetje t\u00eb \u00e7ipave ARM t\u00eb Apple dhe lideri i projektit Ashai Linux, si nj\u00eb opsion p\u00ebr zgjidhjen e konfliktit, propozoi q\u00eb t\u00eb arrij\u00eb pranimin e mb\u00ebshtetjes direkt p\u00ebrmes Linus Torvalds, duke anashkaluar mb\u00ebshtet\u00ebsin e sistemit DMA. N\u00ebse Linus pranon nj\u00eb shkelje t\u00eb till\u00eb t\u00eb subordino, kjo mund t\u00eb \u00e7oj\u00eb n\u00eb nj\u00eb kriz\u00eb menaxhimi n\u00eb zhvillimin e b\u00ebrtham\u00ebs, e n\u00ebse refuzon - do t\u00eb ndaloj\u00eb avancimin e Rust n\u00eb b\u00ebrtham\u00eb. <\/p>\n
Si e nj\u00eb mund\u00ebsi, Hektori p\u00ebrmendi t\u00ebrheqjen e Kristofit n\u00eb p\u00ebrgjegj\u00ebsi p\u00ebr shkeljen e kodeksit t\u00eb sjelljes p\u00ebr shkak t\u00eb nj\u00eb komenti, n\u00eb t\u00eb cilin Kristofi e krahasoi Rustin me nj\u00eb tumor kanceroz. P\u00ebr m\u00eb tep\u00ebr, Hektori shkroi se \u00ebsht\u00eb lodhur nga t\u00eb gjitha burokracit\u00eb, nuk \u00ebsht\u00eb i gatsh\u00ebm ta besoj\u00eb thjesht procesin e vendosur dhe sugjeroi t\u00ebrheqjen e mediave sociale. Dejv Eirli (Dave Airlie), mbajt\u00ebsi i n\u00ebnsistemit DRM, k\u00ebshilloi q\u00eb t\u00eb mos e fryjn\u00eb konfliktin dhe t\u00eb kuptojn\u00eb se comportamenti toksik nuk \u00ebsht\u00eb i pranuesh\u00ebm nga asnj\u00ebra pal\u00eb, pavar\u00ebsisht n\u00ebse diskutanti \u00ebsht\u00eb i drejt\u00eb apo jo. <\/p>\n
N\u00eb diskutim iu bashkua Linus Torvalds, i cili theksoi se problemi mund t\u00eb jet\u00eb te Hektor dhe vet\u00ebk\u00ebnaq\u00ebsia e tij se di\u00e7ka m\u00eb mir\u00eb se t\u00eb tjer\u00ebt, dhe jo n\u00eb procesin aktual t\u00eb zhvillimit t\u00eb b\u00ebrtham\u00ebs, i cili funksionon. Procesi i zhvillimit t\u00eb b\u00ebrtham\u00ebs ka probleme, por kjo \u00ebsht\u00eb nj\u00eb realitet i jet\u00ebs - n\u00eb jet\u00eb nuk ka asgj\u00eb perfekte. P\u00ebrpjekjet p\u00ebr ngacmim p\u00ebrmes rrjeteve sociale - jan\u00eb ato q\u00eb i heqin d\u00ebshir\u00ebn Linus-it p\u00ebr t\u00eb pasur ndonj\u00eb lidhje me qasjen e Hektorit. R\u00ebnd\u00ebsi p\u00ebr Linus-in kan\u00eb diskutimet teknike dhe patch-et, jo presioni p\u00ebrmes rrjeteve sociale. <\/p>\n