Re: OpenAFS client softlockup on concurrential file-system patterns (100% CPU in kernel mode)
Ciprian Dorin Craciun <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.general |
|---|---|
| Message-ID | <CA+Tk8fw6sBOJ4voj9csgM8w1b-WYdw5wCbPQkmcR_=Jy31HvRg@mail.gmail.com> |
On Wed, Nov 20, 2019 at 9:37 PM Ciprian Dorin Craciun <[email protected]> wrote: > Now the client works OK, however if I start the `afsd` client on the > server itself (i.e. over `loopback` network), where previously (with > `-jumbo`) I was able to max-out the disks (~300 MiB/s), now seems to > be capped at around ~120MiB. (The packet-per-second is aroun > ~120K...) Minor correction (only to the item above, the rest still stands), restarting the `afsd` cache on the server itself (thus over `loopback`), I once again am able to max-out the disks (read only). (For some reason this wasn't the case in the previous test...) (It's not the benchmark, as I read large ~20MiB files with 16 concurrent readers, and the same command was used in both test-cases.) Ciprian.