From: Tom Talpey <tom@talpey.com>
To: David Howells <dhowells@redhat.com>, Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org,
Rohith Surabattula <rohiths.msft@gmail.com>,
Shyam Prasad N <nspmangalore@gmail.com>,
Steve French <sfrench@samba.org>,
Jeff Layton <jlayton@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] cifs: Use iov_iters down to the network transport
Date: Wed, 25 May 2022 11:32:38 -0400 [thread overview]
Message-ID: <146bd483-e7d6-0c0d-865a-e43124cc06ae@talpey.com> (raw)
In-Reply-To: <165348876794.2106726.9240233279581920208.stgit@warthog.procyon.org.uk>
On 5/25/2022 10:26 AM, David Howells wrote:> There's also a couple of
changes in patch 7 from Namjae Jeon to make
> soft-iWarp work. Feel free to discard that patch if you get a better version
> from him.
I think we should send that patch directly, and not include it
here. I actually have some comments/suggestions on it, and the
client sge handling, which I'd like to discuss separately.
It's fine to keep it here temporarily, but it should be dropped
once this series moves forward.
Tom.
prev parent reply other threads:[~2022-05-25 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 14:26 [PATCH 0/7] cifs: Use iov_iters down to the network transport David Howells
2022-05-25 14:26 ` [PATCH 1/7] iov_iter: Add a function to extract an iter's buffers to a bvec iter David Howells
2022-05-25 14:26 ` [PATCH 2/7] iov_iter: Add a general purpose iteration function David Howells
2022-05-25 14:26 ` [PATCH 3/7] cifs: Add some helper functions David Howells
2022-05-25 14:26 ` [PATCH 4/7] cifs: Add a function to read into an iter from a socket David Howells
2022-05-25 14:26 ` [PATCH 5/7] cifs: Change the I/O paths to use an iterator rather than a page list David Howells
2022-05-25 14:26 ` [PATCH 6/7] cifs: Remove unused code David Howells
2022-05-25 14:26 ` [PATCH 7/7] cifs, ksmbd: Fix MAX_SGE count for softiwarp David Howells
2022-05-25 15:32 ` Tom Talpey [this message]
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=146bd483-e7d6-0c0d-865a-e43124cc06ae@talpey.com \
--to=tom@talpey.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=rohiths.msft@gmail.com \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.