From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 1/8] lib: Introduce sgl_alloc() and sgl_free()
Date: Thu, 12 Oct 2017 23:00:10 +0000 [thread overview]
Message-ID: <1507849209.14112.1.camel@wdc.com> (raw)
In-Reply-To: <ee12eeaf-9848-478d-4ebe-9d3497e248e0@kernel.dk>
On Thu, 2017-10-12 at 16:52 -0600, Jens Axboe wrote:
> On 10/12/2017 04:45 PM, Bart Van Assche wrote:
> > +++ b/include/linux/sgl_alloc.h
> > @@ -0,0 +1,16 @@
> > +#ifndef _SGL_ALLOC_H_
> > +#define _SGL_ALLOC_H_
> > +
> > +#include <linux/types.h> /* bool, gfp_t */
> > +
> > +struct scatterlist;
> > +
> > +struct scatterlist *sgl_alloc_order(unsigned long long length,
> > + unsigned int order, unsigned int *nent_p,
> > + gfp_t gfp, bool chainable);
> > +struct scatterlist *sgl_alloc(unsigned long long length, unsigned int *nent_p,
> > + gfp_t gfp);
> > +void sgl_free_order(struct scatterlist *sgl, int order);
> > +void sgl_free(struct scatterlist *sgl);
> > +
> > +#endif /* _SGL_ALLOC_H_ */
>
> Should this just go into linux/scatterlist.h instead of creating a new header
> file?
That's something I can change. I don't have a strong opinion about whether
these declarations should go into a new header file or into linux/scatterlist.h.
Bart.
next prev parent reply other threads:[~2017-10-12 23:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 22:45 [PATCH 0/8] Introduce sgl_alloc() and sgl_free() Bart Van Assche
2017-10-12 22:45 ` [PATCH 1/8] lib: " Bart Van Assche
2017-10-12 22:52 ` Jens Axboe
2017-10-12 23:00 ` Bart Van Assche [this message]
2017-10-13 8:44 ` Johannes Thumshirn
2017-10-13 14:20 ` Jens Axboe
2017-10-13 17:43 ` Randy Dunlap
2017-10-13 17:56 ` Bart Van Assche
2017-10-12 22:45 ` [PATCH 2/8] crypto: scompress - use " Bart Van Assche
2017-10-12 22:45 ` [PATCH 3/8] nvmet/fc: Use " Bart Van Assche
2017-10-13 8:41 ` Johannes Thumshirn
2017-10-12 22:45 ` [PATCH 4/8] nvmet/rdma: " Bart Van Assche
2017-10-13 8:42 ` Johannes Thumshirn
2017-10-12 22:45 ` [PATCH 5/8] target: Use sgl_alloc_order() " Bart Van Assche
2017-10-12 22:45 ` [PATCH 6/8] scsi/ipr: Use sgl_alloc_order() and sgl_free_order() Bart Van Assche
2017-10-13 8:45 ` Johannes Thumshirn
2017-10-12 22:45 ` [PATCH 7/8] scsi/pmcraid: Remove an unused structure member Bart Van Assche
2017-10-13 8:45 ` Johannes Thumshirn
2017-10-12 22:45 ` [PATCH 8/8] scsi/pmcraid: Use sgl_alloc_order() and sgl_free_order() Bart Van Assche
2017-10-13 8:47 ` Johannes Thumshirn
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=1507849209.14112.1.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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).