Multi-protocol support for transactions
US-2020293465-A1 · Sep 17, 2020 · US
US2022345538A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2022345538-A1 |
| Application number | US-202117239102-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 23, 2021 |
| Priority date | Apr 23, 2021 |
| Publication date | Oct 27, 2022 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method, computer program product, and computer system for using, by a computing device, free central processing unit (CPU) cycles for processing Non-Volatile Memory express Over Fiber (NVMeoF)/Transmission Control Protocol (TCP) sockets. Using the free CPU cycles for processing the NVMeoF/TCP sockets may include exposing a character device with a callback that iterates over the NVMeoF/TCP sockets for processing.
Opening claim text (preview).
1 . A computer-implemented method comprising: using, by a computing device, free central processing unit (CPU) cycles for processing Non-Volatile Memory express Over Fiber (NVMeoF)/Transmission Control Protocol (TCP) sockets; wherein using the free CPU cycles for processing the NVMeoF/TCP sockets includes exposing a character device with a callback that iterates over the NVMeoF/TCP sockets for processing; and adding the NVMeoF/TCP sockets to a waiting list, wherein each of the NVMeoF/TCP sockets holds an atomic state and each of the NVMeoF/TCP sockets is configured to be processed by a storage management application thread or a kernel thread (kthread). 2 . The computer-implemented method of claim 1 wherein the callback includes an Input Output Control (IOCTL) callback. 3 . (canceled) 4 . The computer-implemented method of claim 2 wherein a software interrupt adds the NVMeoF/TCP sockets to the waiting list to process the NVMeoF/TCP sockets upon the IOCTL callback being called by a storage application thread. 5 . The computer-implemented method of claim 4 wherein the software interrupt is processed by a frontend CPU core. 6 . The computer-implemented method of claim 2 wherein the kthread is woken up by a software interrupt based upon, at least in part, adding the NVMeoF/TCP sockets to the waiting list. 7 . (canceled) 8 . A computer program product residing on a non-transitory computer readable storage medium having a plurality of instructions stored thereon which, when executed across one or more processors, causes at least a portion of the one or more processors to perform operations comprising: using free central processing unit (CPU) cycles for processing Non-Volatile Memory express Over Fiber (NVMeoF)/Transmission Control Protocol (TCP) sockets; wherein using the free CPU cycles for processing the NVMeoF/TCP sockets includes exposing a character device with a callback that iterates over the NVMeoF/TCP sockets for processing; and adding the NVMeoF/TCP sockets to a waiting list, wherein each of the NVMeoF/TCP sockets holds an atomic state and each of the NVMeoF/TCP sockets is configured to be processed by a storage management application thread or a kernel thread (kthread). 9 . The computer program product of claim 8 wherein the callback includes an Input Output Control (IOCTL) callback. 10 . (canceled) 11 . The computer program product of claim 9 wherein a software interrupt adds the NVMeoF/TCP sockets to the waiting list to process the NVMeoF/TCP sockets upon the IOCTL callback being called by a storage application thread. 12 . The computer program product of claim 11 wherein the software interrupt is processed by a frontend CPU core. 13 . The computer program product of claim 9 wherein the kthread is woken up by a software interrupt based upon, at least in part, adding the NVMeoF/TCP sockets to the waiting list. 14 . (canceled) 15 . A computing system including one or more processors and one or more memories configured to perform operations comprising: using free central processing unit (CPU) cycles for processing Non-Volatile Memory express Over Fiber (NVMeoF)/Transmission Control Protocol (TCP) sockets; wherein using the free CPU cycles for processing the NVMeoF/TCP sockets includes exposing a character device with a callback that iterates over the NVMeoF/TCP sockets for processing, wherein the callback includes an Input Output Control (IOCTL) callback; and adding the NVMeoF/TCP sockets to a waiting list, wherein a software interrupt adds the NVMeoF/TCP sockets to the waiting list to process the NVMeoF/TCP sockets upon the IOCTL callback being called by a storage application thread. 16 . (canceled) 17 . (canceled) 18 . The computing system of claim 15 wherein the software interrupt is processed by a frontend CPU core. 19 . The computing system of claim 15 wherein a kernel thread (kthread) is woken up by the software interrupt based upon, at least in part, adding the NVMeoF/TCP sockets to the waiting list. 20 . The computing system of claim 19 wherein each of the NVMeoF/TCP sockets holds an atomic state.
by interrupt, e.g. masked · CPC title
Discovery involving ranked list compilation of candidate peers · CPC title
Protocols for remote procedure calls [RPC] · CPC title
Task transfer initiation or dispatching · CPC title
for remote control or remote monitoring of applications · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.