All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Jens Axboe <axboe@kernel.dk>, SeongJae Park <sjpark@amazon.com>,
	konrad.wilk@oracle.com, pdurrant@amazon.com,
	SeongJae Park <sjpark@amazon.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH v5 1/2] xenbus/backend: Add memory pressure handler callback
Date: Tue, 10 Dec 2019 11:24:37 +0100	[thread overview]
Message-ID: <CAEjAshqsdjANuZDJwUnTgh3FBnhN-fp6T7-oN0hZKq8uHMDWhA@mail.gmail.com> (raw)
In-Reply-To: <20191210102023.GF980@Air-de-Roger>

On Tue, Dec 10, 2019 at 11:21 AM Roger Pau Monné <roger.pau@citrix.com> wrote:
>
> On Tue, Dec 10, 2019 at 11:16:35AM +0100, Roger Pau Monné wrote:
> > On Tue, Dec 10, 2019 at 08:06:27AM +0000, SeongJae Park wrote:
> > > diff --git a/include/xen/xenbus.h b/include/xen/xenbus.h
> > > index 869c816d5f8c..cdb075e4182f 100644
> > > --- a/include/xen/xenbus.h
> > > +++ b/include/xen/xenbus.h
> > > @@ -104,6 +104,7 @@ struct xenbus_driver {
> > >     struct device_driver driver;
> > >     int (*read_otherend_details)(struct xenbus_device *dev);
> > >     int (*is_ready)(struct xenbus_device *dev);
> > > +   unsigned (*reclaim)(struct xenbus_device *dev);
> >
> > ... hence I wonder why it's returning an unsigned when it's just
> > ignored.
> >
> > IMO it should return an int to signal errors, and the return should be
> > ignored.
>
> Meant to write 'shouldn't be ignored' sorry.

Thanks for good opinions and comments!  I will apply your comments in the next
version.


Thanks,
SeongJae Park

>
> Roger.

WARNING: multiple messages have this Message-ID (diff)
From: SeongJae Park <sj38.park@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Jens Axboe <axboe@kernel.dk>, SeongJae Park <sjpark@amazon.com>,
	konrad.wilk@oracle.com, pdurrant@amazon.com,
	SeongJae Park <sjpark@amazon.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH v5 1/2] xenbus/backend: Add memory pressure handler callback
Date: Tue, 10 Dec 2019 11:24:37 +0100	[thread overview]
Message-ID: <CAEjAshqsdjANuZDJwUnTgh3FBnhN-fp6T7-oN0hZKq8uHMDWhA@mail.gmail.com> (raw)
In-Reply-To: <20191210102023.GF980@Air-de-Roger>

On Tue, Dec 10, 2019 at 11:21 AM Roger Pau Monné <roger.pau@citrix.com> wrote:
>
> On Tue, Dec 10, 2019 at 11:16:35AM +0100, Roger Pau Monné wrote:
> > On Tue, Dec 10, 2019 at 08:06:27AM +0000, SeongJae Park wrote:
> > > diff --git a/include/xen/xenbus.h b/include/xen/xenbus.h
> > > index 869c816d5f8c..cdb075e4182f 100644
> > > --- a/include/xen/xenbus.h
> > > +++ b/include/xen/xenbus.h
> > > @@ -104,6 +104,7 @@ struct xenbus_driver {
> > >     struct device_driver driver;
> > >     int (*read_otherend_details)(struct xenbus_device *dev);
> > >     int (*is_ready)(struct xenbus_device *dev);
> > > +   unsigned (*reclaim)(struct xenbus_device *dev);
> >
> > ... hence I wonder why it's returning an unsigned when it's just
> > ignored.
> >
> > IMO it should return an int to signal errors, and the return should be
> > ignored.
>
> Meant to write 'shouldn't be ignored' sorry.

Thanks for good opinions and comments!  I will apply your comments in the next
version.


Thanks,
SeongJae Park

>
> Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-12-10 10:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  8:06 [PATCH v5 0/2] xenbus/backend: Add a memory pressure handler callback SeongJae Park
2019-12-10  8:06 ` [Xen-devel] " SeongJae Park
2019-12-10  8:06 ` [PATCH v5 1/2] xenbus/backend: Add " SeongJae Park
2019-12-10  8:06   ` [Xen-devel] " SeongJae Park
2019-12-10  8:17   ` Jürgen Groß
2019-12-10  8:17     ` [Xen-devel] " Jürgen Groß
2019-12-10 10:16   ` Roger Pau Monné
2019-12-10 10:16     ` [Xen-devel] " Roger Pau Monné
2019-12-10 10:21     ` Roger Pau Monné
2019-12-10 10:21       ` Roger Pau Monné
2019-12-10 10:24       ` SeongJae Park [this message]
2019-12-10 10:24         ` SeongJae Park
2019-12-11  3:50     ` SeongJae Park
2019-12-11  3:50       ` [Xen-devel] " SeongJae Park
2019-12-11 10:51       ` Roger Pau Monné
2019-12-11 10:51         ` [Xen-devel] " Roger Pau Monné
2019-12-11 11:52         ` Re: " SeongJae Park
2019-12-11 11:52           ` [Xen-devel] " SeongJae Park
2019-12-10  8:06 ` [PATCH v5 2/2] xen/blkback: Squeeze page pools if a memory pressure is detected SeongJae Park
2019-12-10  8:06   ` [Xen-devel] " SeongJae Park
2019-12-10 11:04   ` Roger Pau Monné
2019-12-10 11:04     ` [Xen-devel] " Roger Pau Monné
2019-12-11  4:08     ` SeongJae Park
2019-12-11  4:08       ` [Xen-devel] " SeongJae Park
2019-12-11 11:14       ` Roger Pau Monné
2019-12-11 11:14         ` [Xen-devel] " Roger Pau Monné
2019-12-11 11:52         ` Re: " SeongJae Park
2019-12-11 11:52           ` [Xen-devel] " 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=CAEjAshqsdjANuZDJwUnTgh3FBnhN-fp6T7-oN0hZKq8uHMDWhA@mail.gmail.com \
    --to=sj38.park@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdurrant@amazon.com \
    --cc=roger.pau@citrix.com \
    --cc=sjpark@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.