From: Anna Schumaker <anna.schumaker@oracle.com>
To: marc eshel <eshel.marc@gmail.com>,
Olga Kornievskaia <aglo@umich.edu>,
schumaker anna <schumaker.anna@gmail.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: issues with Linux client pNFS
Date: Mon, 16 Sep 2024 16:33:38 -0400 [thread overview]
Message-ID: <6880c031-3936-4ea1-86f2-5dc6050c9051@oracle.com> (raw)
In-Reply-To: <41ee5118-027b-4630-8f02-b3a67c61b328@gmail.com>
Hi Marc,
On 9/16/24 4:27 PM, marc eshel wrote:
> Hi,
>
> Who is the current maintainer of the Linux NFS client?
That would be me and Trond.
>
> I have an issue with the way pNFS client is distributing the reads among the DSs and I can provide the traces if anyone cares.
What is the problem? And sure, send along the traces! I'll try to take a look as soon as I can.
Anna
>
> Thanks, Marc.
>
next prev parent reply other threads:[~2024-09-16 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 20:27 issues with Linux client pNFS marc eshel
2024-09-16 20:33 ` Anna Schumaker [this message]
2024-09-16 21:51 ` marc eshel
2026-09-16 22:30 ` marc eshel
2026-09-17 13:29 ` Anna Schumaker
2026-09-17 15:42 ` marc eshel
2026-09-17 19:00 ` marc eshel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6880c031-3936-4ea1-86f2-5dc6050c9051@oracle.com \
--to=anna.schumaker@oracle.com \
--cc=aglo@umich.edu \
--cc=eshel.marc@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox