linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Connor Kuehl <ckuehl@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: virtio-fs@redhat.com, stefanha@redhat.com, miklos@szeredi.hu,
	virtualization@lists.linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question about sg_count_fuse_req() in linux/fs/fuse/virtio_fs.c
Date: Thu, 18 Mar 2021 08:58:54 -0500	[thread overview]
Message-ID: <19c488d0-2006-4a96-610d-f4825aa43cb3@redhat.com> (raw)
In-Reply-To: <20210318135600.GA368102@redhat.com>

On 3/18/21 8:56 AM, Vivek Goyal wrote:
> I think all the in args are being mapped into a single scatter gather
> element and that's why it does not matter whether in_numargs is 3, 2 or 1.
> They will be mapped in a single element.
> 
> sg_init_fuse_args()
> {
>          len = fuse_len_args(numargs - argpages, args);
>          if (len)
>                  sg_init_one(&sg[total_sgs++], argbuf, len);
> }
> 
>          out_sgs += sg_init_fuse_args(&sg[out_sgs], req,
>                                       (struct fuse_arg *)args->in_args,
>                                       args->in_numargs, args->in_pages,
>                                       req->argbuf, &argbuf_used);
> 
> When we are sending some data in some pages, then we set args->in_pages
> to true. And in that case, last element of args->in_args[] contains the
> total size of bytes in additional pages we are sending and is not part
> of in_args being mapped to scatter gather element. That's why this
> check.
> 
> 	if (args->in_numargs - args->in_pages)
> 		total_sgs += 1;

Aha! Thank you, Vivek. That makes sense.

> Not sure when we will have a case where args->in_numargs = 1 and
> args->in_pages=true. Do we ever hit that.

Not in my experience. My previous mail was examining this routine mainly 
in a vacuum.

Connor

> Thanks
> Vivek
> 
>>
>> 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
>>
> 


      reply	other threads:[~2021-03-18 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 18:12 Question about sg_count_fuse_req() in linux/fs/fuse/virtio_fs.c Connor Kuehl
2021-03-18 13:56 ` Vivek Goyal
2021-03-18 13:58   ` Connor Kuehl [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=19c488d0-2006-4a96-610d-f4825aa43cb3@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).