From: Long Li <longli@microsoft.com>
To: Tom Talpey <tom@talpey.com>, Steve French <sfrench@samba.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
"samba-technical@lists.samba.org"
<samba-technical@lists.samba.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: RE: [Patch v2 04/15] CIFS: Add support for direct pages in wdata
Date: Mon, 25 Jun 2018 20:34:06 +0000 [thread overview]
Message-ID: <CY4PR2101MB0722C0EBEDF150DCD5E88A8ECE4A0@CY4PR2101MB0722.namprd21.prod.outlook.com> (raw)
In-Reply-To: <4edad13c-e257-ff1c-223a-324f484a936a@talpey.com>
> Subject: Re: [Patch v2 04/15] CIFS: Add support for direct pages in wdata
>
> On 5/30/2018 3:47 PM, Long Li wrote:
> > From: Long Li <longli@microsoft.com>
> >
> > Add a function to allocate wdata without allocating pages for data
> > transfer. This gives the caller an option to pass a number of pages
> > that point to the data buffer to write to.
> >
> > wdata is reponsible for free those pages after it's done.
>
> Same comment as for the earlier patch. "Caller" is responsible for "freeing"
> those pages? Confusing, as worded.
>
> >
> > Signed-off-by: Long Li <longli@microsoft.com>
> > ---
> > fs/cifs/cifsglob.h | 2 +-
> > fs/cifs/cifsproto.h | 2 ++
> > fs/cifs/cifssmb.c | 17 ++++++++++++++---
> > 3 files changed, 17 insertions(+), 4 deletions(-)
> >
> > diff --git a/fs/cifs/cifsglob.h b/fs/cifs/cifsglob.h index
> > 56864a87..7f62c98 100644
> > --- a/fs/cifs/cifsglob.h
> > +++ b/fs/cifs/cifsglob.h
> > @@ -1205,7 +1205,7 @@ struct cifs_writedata {
> > unsigned int tailsz;
> > unsigned int credits;
> > unsigned int nr_pages;
> > - struct page *pages[];
> > + struct page **pages;
>
> Also same comment as for earlier patch, these are syntactically equivalent
> and maybe not needed to change.
>
> > };
> >
> > /*
> > diff --git a/fs/cifs/cifsproto.h b/fs/cifs/cifsproto.h index
> > 1f27d8e..7933c5f 100644
> > --- a/fs/cifs/cifsproto.h
> > +++ b/fs/cifs/cifsproto.h
> > @@ -533,6 +533,8 @@ int cifs_async_writev(struct cifs_writedata *wdata,
> > void cifs_writev_complete(struct work_struct *work);
> > struct cifs_writedata *cifs_writedata_alloc(unsigned int nr_pages,
> > work_func_t complete);
> > +struct cifs_writedata *cifs_writedata_direct_alloc(struct page **pages,
> > + work_func_t complete);
> > void cifs_writedata_release(struct kref *refcount);
> > int cifs_query_mf_symlink(unsigned int xid, struct cifs_tcon *tcon,
> > struct cifs_sb_info *cifs_sb,
> > diff --git a/fs/cifs/cifssmb.c b/fs/cifs/cifssmb.c index
> > c8e4278..5aca336 100644
> > --- a/fs/cifs/cifssmb.c
> > +++ b/fs/cifs/cifssmb.c
> > @@ -1952,6 +1952,7 @@ cifs_writedata_release(struct kref *refcount)
> > if (wdata->cfile)
> > cifsFileInfo_put(wdata->cfile);
> >
> > + kvfree(wdata->pages);
> > kfree(wdata);
> > }
> >
> > @@ -2075,12 +2076,22 @@ cifs_writev_complete(struct work_struct
> *work)
> > struct cifs_writedata *
> > cifs_writedata_alloc(unsigned int nr_pages, work_func_t complete)
> > {
> > + struct page **pages =
> > + kzalloc(sizeof(struct page *) * nr_pages, GFP_NOFS);
>
> Why do you do a GFP_NOFS here but GFP_KERNEL in the earlier patch?
This is for the I/O write path. The earlier patch is for I/O read path. This code preserves the behavior from the buffer I/O code.
The write path is possibly used when memory is under pressure, so it's better not to call FS (and CIFS) that may result in a loop.
>
> > + if (pages)
> > + return cifs_writedata_direct_alloc(pages, complete);
> > +
> > + return NULL;
> > +}
> > +
> > +struct cifs_writedata *
> > +cifs_writedata_direct_alloc(struct page **pages, work_func_t
> > +complete) {
> > struct cifs_writedata *wdata;
> >
> > - /* writedata + number of page pointers */
> > - wdata = kzalloc(sizeof(*wdata) +
> > - sizeof(struct page *) * nr_pages, GFP_NOFS);
> > + wdata = kzalloc(sizeof(*wdata), GFP_NOFS);
> > if (wdata != NULL) {
> > + wdata->pages = pages;
> > kref_init(&wdata->refcount);
> > INIT_LIST_HEAD(&wdata->list);
> > init_completion(&wdata->done);
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the
> body of a message to majordomo@vger.kernel.org More majordomo info at
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger.ke
> rnel.org%2Fmajordomo-
> info.html&data=02%7C01%7Clongli%40microsoft.com%7C20e0bcbdcce3
> 402133ee08d5d9767977%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%
> 7C636654025229749549&sdata=p4P9AqS8cnOHErCFc1XALeaZxHuB7%2B
> VOF10SjaaycAI%3D&reserved=0
next prev parent reply other threads:[~2018-06-25 20:34 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 19:47 [Patch v2 00/15] CIFS: Add direct I/O support Long Li
2018-05-30 19:47 ` [Patch v2 01/15] CIFS: Introduce offset for the 1st page in data transfer structures Long Li
2018-05-30 19:47 ` [Patch v2 02/15] CIFS: Add support for direct pages in rdata Long Li
2018-05-30 20:27 ` Ruhl, Michael J
2018-05-30 20:57 ` Long Li
2018-06-24 1:50 ` Tom Talpey
2018-06-25 20:25 ` Long Li
2018-06-25 21:01 ` Jason Gunthorpe
2018-06-26 15:13 ` Tom Talpey
2018-06-27 3:21 ` Long Li
2018-05-30 19:47 ` [Patch v2 03/15] CIFS: Use offset when reading pages Long Li
2018-06-24 1:58 ` Tom Talpey
2018-06-25 20:27 ` Long Li
2018-05-30 19:47 ` [Patch v2 04/15] CIFS: Add support for direct pages in wdata Long Li
2018-06-24 2:01 ` Tom Talpey
2018-06-25 20:34 ` Long Li [this message]
2018-05-30 19:47 ` [Patch v2 05/15] CIFS: Calculate the correct request length based on page offset and tail size Long Li
2018-06-24 2:07 ` Tom Talpey
2018-06-25 21:07 ` Long Li
2018-05-30 19:47 ` [Patch v2 06/15] CIFS: Introduce helper function to get page offset and length in smb_rqst Long Li
2018-06-24 2:09 ` Tom Talpey
2018-06-25 21:14 ` Long Li
2018-06-26 13:16 ` Tom Talpey
2018-06-27 3:24 ` Long Li
2018-05-30 19:47 ` [Patch v2 07/15] CIFS: When sending data on socket, pass the correct page offset Long Li
2018-05-30 19:48 ` [Patch v2 08/15] CIFS: SMBD: Support page offset in RDMA send Long Li
2018-06-24 2:11 ` Tom Talpey
2018-06-25 21:23 ` Long Li
2018-05-30 19:48 ` [Patch v2 09/15] CIFS: SMBD: Support page offset in RDMA recv Long Li
2018-06-24 2:16 ` Tom Talpey
2018-06-25 21:29 ` Long Li
2018-05-30 19:48 ` [Patch v2 10/15] CIFS: SMBD: Support page offset in memory registration Long Li
2018-06-24 2:24 ` Tom Talpey
2018-05-30 19:48 ` [Patch v2 11/15] CIFS: Pass page offset for calculating signature Long Li
2018-06-24 2:27 ` Tom Talpey
2018-06-26 4:15 ` Long Li
2018-05-30 19:48 ` [Patch v2 12/15] CIFS: Pass page offset for encrypting Long Li
2018-06-24 2:28 ` Tom Talpey
2018-05-30 19:48 ` [Patch v2 13/15] CIFS: Add support for direct I/O read Long Li
2018-06-02 5:51 ` kbuild test robot
2018-06-02 7:15 ` kbuild test robot
2018-06-24 2:39 ` Tom Talpey
2018-06-26 4:34 ` Long Li
2018-05-30 19:48 ` [Patch v2 14/15] CIFS: Add support for direct I/O write Long Li
2018-06-24 2:48 ` Tom Talpey
2018-06-26 4:39 ` Long Li
2018-06-26 13:29 ` Tom Talpey
2018-06-27 3:44 ` Long Li
2018-05-30 19:48 ` [Patch v2 15/15] CIFS: Add direct I/O functions to file_operations Long Li
2018-06-07 11:17 ` Pavel Shilovsky
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=CY4PR2101MB0722C0EBEDF150DCD5E88A8ECE4A0@CY4PR2101MB0722.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=tom@talpey.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;
as well as URLs for NNTP newsgroup(s).