From: Ian Campbell <ian.campbell@citrix.com>
To: Imre Palik <imrep.amz@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>, <xen-devel@lists.xenproject.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Palik, Imre" <imrep@amazon.de>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [RFC PATCH] xen-netback: making the bandwidth limiter runtime settable
Date: Tue, 17 Mar 2015 11:26:44 +0000 [thread overview]
Message-ID: <1426591604.18247.192.camel@citrix.com> (raw)
In-Reply-To: <1426251065-24279-1-git-send-email-imrep.amz@gmail.com>
On Fri, 2015-03-13 at 13:51 +0100, Imre Palik wrote:
[...]
> diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c
> index 3aa8648..34d8038 100644
> --- a/drivers/net/xen-netback/interface.c
> +++ b/drivers/net/xen-netback/interface.c
> @@ -463,6 +463,7 @@ int xenvif_init_queue(struct xenvif_queue *queue)
> queue->credit_bytes = queue->remaining_credit = ~0UL;
> queue->credit_usec = 0UL;
> init_timer(&queue->credit_timeout);
> + queue->credit_timeout.function = xenvif_tx_credit_callback;
> queue->credit_window_start = get_jiffies_64();
>
> queue->rx_queue_max = XENVIF_RX_QUEUE_BYTES;
> diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
> index cab9f52..bcc1880 100644
> --- a/drivers/net/xen-netback/netback.c
> +++ b/drivers/net/xen-netback/netback.c
[...]
> @@ -1170,7 +1170,7 @@ static bool tx_credit_exceeded(struct xenvif_queue *queue, unsigned size)
> queue->credit_timeout.data =
> (unsigned long)queue;
> queue->credit_timeout.function =
> - tx_credit_callback;
> + xenvif_tx_credit_callback;
Are this init and the one in xenvif_init_queue really both needed?
Ian.
prev parent reply other threads:[~2015-03-17 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 12:51 [RFC PATCH] xen-netback: making the bandwidth limiter runtime settable Imre Palik
2015-03-17 11:17 ` Wei Liu
2015-03-18 16:21 ` Imre Palik
2015-03-18 16:28 ` Wei Liu
2015-03-17 11:26 ` Ian Campbell [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=1426591604.18247.192.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=aliguori@amazon.com \
--cc=imrep.amz@gmail.com \
--cc=imrep@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--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