From: Connor Kuehl <ckuehl@redhat.com>
To: virtio-fs@redhat.com
Cc: vgoyal@redhat.com, stefanha@redhat.com, miklos@szeredi.hu,
virtualization@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Question about sg_count_fuse_req() in linux/fs/fuse/virtio_fs.c
Date: Wed, 17 Mar 2021 13:12:01 -0500 [thread overview]
Message-ID: <810089e0-3a09-0d8f-9f8e-be5b3ac70587@redhat.com> (raw)
Hi,
I've been familiarizing myself with the virtiofs guest kernel module and
I'm trying to better understand how virtiofs maps a FUSE request into
scattergather lists.
sg_count_fuse_req() starts knowing that there will be at least one in
header, as shown here (which makes sense):
unsigned int size, total_sgs = 1 /* fuse_in_header */;
However, I'm confused about this snippet right beneath it:
if (args->in_numargs - args->in_pages)
total_sgs += 1;
What is the significance of the sg that is needed in the cases where
this branch is taken? I'm not sure what its relationship is with
args->in_numargs since it will increment total_sgs regardless
args->in_numargs is 3, 2, or even 1 if args->in_pages is false.
Especially since the block right below it counts pages if args->in_pages
is true:
if (args->in_pages) {
size = args->in_args[args->in_numargs - 1].size;
total_sgs += sg_count_fuse_pages(ap->descs, ap->num_pages,
size);
}
The rest of the routine goes on similarly but for the 'out' components.
I doubt incrementing 'total_sgs' in the first if-statement I showed
above is vestigial, I just think my mental model of what is happening
here is incomplete.
Any clarification is much appreciated!
Connor
next reply other threads:[~2021-03-17 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 18:12 Connor Kuehl [this message]
2021-03-18 13:56 ` Question about sg_count_fuse_req() in linux/fs/fuse/virtio_fs.c Vivek Goyal
2021-03-18 13:58 ` Connor Kuehl
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=810089e0-3a09-0d8f-9f8e-be5b3ac70587@redhat.com \
--to=ckuehl@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).