public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sjpark@amazon.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: SeongJae Park <sjpark@amazon.com>, <konrad.wilk@oracle.com>,
	<roger.pau@citrix.com>, SeongJae Park <sjpark@amazon.de>,
	<axboe@kernel.dk>, <aliguori@amazon.com>, <amit@kernel.org>,
	<mheyne@amazon.de>, <pdurrant@amazon.co.uk>,
	<linux-block@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] xen-blkfront: add a parameter for disabling of persistent grants
Date: Tue, 22 Sep 2020 16:31:17 +0200	[thread overview]
Message-ID: <20200922143117.30167-1-sjpark@amazon.com> (raw)
In-Reply-To: <28773bff-7664-99fa-a542-b87e907bf705@suse.com>

On Tue, 22 Sep 2020 16:27:03 +0200 "Jürgen Groß" <jgross@suse.com> wrote:

> On 22.09.20 16:15, SeongJae Park wrote:
> > From: SeongJae Park <sjpark@amazon.de>
> > 
> > Persistent grants feature provides high scalability.  On some small
> > systems, however, it could incur data copy overheads[1] and thus it is
> > required to be disabled.  It can be disabled from blkback side using a
> > module parameter, 'feature_persistent'.  But, it is impossible from
> > blkfront side.  For the reason, this commit adds a blkfront module
> > parameter for disabling of the feature.
> > 
> > [1] https://wiki.xen.org/wiki/Xen_4.3_Block_Protocol_Scalability
> > 
> > Signed-off-by: SeongJae Park <sjpark@amazon.de>
> > ---
> >   .../ABI/testing/sysfs-driver-xen-blkfront     |  9 +++++++++
> >   drivers/block/xen-blkfront.c                  | 20 ++++++++++++++-----
> >   2 files changed, 24 insertions(+), 5 deletions(-)
> > 
> > diff --git a/Documentation/ABI/testing/sysfs-driver-xen-blkfront b/Documentation/ABI/testing/sysfs-driver-xen-blkfront
> > index c0a6cb7eb314..9c31334cb2e6 100644
> > --- a/Documentation/ABI/testing/sysfs-driver-xen-blkfront
> > +++ b/Documentation/ABI/testing/sysfs-driver-xen-blkfront
> > @@ -8,3 +8,12 @@ Description:
> >                   is 32 - higher value means more potential throughput but more
> >                   memory usage. The backend picks the minimum of the frontend
> >                   and its default backend value.
> > +
> > +What:           /sys/module/xen_blkfront/parameters/feature_persistent
> > +Date:           September 2020
> > +KernelVersion:  5.10
> > +Contact:        SeongJae Park <sjpark@amazon.de>
> > +Description:
> > +                Whether to enable the persistent grants feature or not.  Note
> > +                that this option only takes effect on newly created frontends.
> > +                The default is Y (enable).
> > diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> > index 91de2e0755ae..b2d3b1262404 100644
> > --- a/drivers/block/xen-blkfront.c
> > +++ b/drivers/block/xen-blkfront.c
> > @@ -1866,8 +1866,8 @@ static int talk_to_blkback(struct xenbus_device *dev,
> >   		message = "writing protocol";
> >   		goto abort_transaction;
> >   	}
> > -	err = xenbus_printf(xbt, dev->nodename,
> > -			    "feature-persistent", "%u", 1);
> > +	err = xenbus_printf(xbt, dev->nodename, "feature-persistent", "%u",
> > +			info->feature_persistent);
> >   	if (err)
> >   		dev_warn(&dev->dev,
> >   			 "writing persistent grants feature to xenbus");
> > @@ -1941,6 +1941,13 @@ static int negotiate_mq(struct blkfront_info *info)
> >   	}
> >   	return 0;
> >   }
> > +
> > +/* Enable the persistent grants feature. */
> > +static bool feature_persistent = true;
> > +module_param(feature_persistent, bool, 0644);
> > +MODULE_PARM_DESC(feature_persistent,
> > +		"Enables the persistent grants feature");
> > +
> >   /**
> >    * Entry point to this code when a new device is created.  Allocate the basic
> >    * structures and the ring buffer for communication with the backend, and
> > @@ -2007,6 +2014,8 @@ static int blkfront_probe(struct xenbus_device *dev,
> >   	info->vdevice = vdevice;
> >   	info->connected = BLKIF_STATE_DISCONNECTED;
> >   
> > +	info->feature_persistent = feature_persistent ? 1 : 0;
> 
> Just use the value.

Yes, I will.

> 
> With that changed:
> 
> Reviewed-by: Juergen Gross <jgross@suse.com>

Appreciate :)


Thanks,
SeongJae Park

  reply	other threads:[~2020-09-22 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 14:15 [PATCH v3 0/3] xen-blk(back|front): Let users disable persistent grants SeongJae Park
2020-09-22 14:15 ` [PATCH v3 1/3] xen-blkback: add a parameter for disabling of " SeongJae Park
2020-09-22 14:25   ` Jürgen Groß
2020-09-22 14:30     ` SeongJae Park
2020-09-22 14:15 ` [PATCH v3 2/3] xen-blkfront: " SeongJae Park
2020-09-22 14:27   ` Jürgen Groß
2020-09-22 14:31     ` SeongJae Park [this message]
2020-09-22 14:15 ` [PATCH v3 3/3] xen-blkfront: Apply changed parameter name to the document SeongJae Park
2020-09-22 14:27   ` Jürgen Groß
2020-09-22 14:44     ` Roger Pau Monné
2020-09-22 15:02       ` SeongJae Park
2020-09-22 14:45 ` [PATCH v3 0/3] xen-blk(back|front): Let users disable persistent grants Roger Pau Monné
2020-09-22 14:52   ` SeongJae Park

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=20200922143117.30167-1-sjpark@amazon.com \
    --to=sjpark@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=amit@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mheyne@amazon.de \
    --cc=pdurrant@amazon.co.uk \
    --cc=roger.pau@citrix.com \
    --cc=sjpark@amazon.de \
    --cc=xen-devel@lists.xenproject.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