public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>
To: Wei Liu <wei.liu2@citrix•com>
Cc: netdev@vger•kernel.org, jeremy@goop•org,
	xen-devel@lists•xensource.com, ian.campbell@citrix•com
Subject: Re: [PATCH] xen-netfront: correct MAX_TX_TARGET calculation.
Date: Thu, 26 Jan 2012 13:19:00 -0500	[thread overview]
Message-ID: <20120126181900.GB25572@phenom.dumpdata.com> (raw)
In-Reply-To: <1327598603-16398-1-git-send-email-wei.liu2@citrix.com>

On Thu, Jan 26, 2012 at 05:23:23PM +0000, Wei Liu wrote:

Can you give some more details please? What is the impact of
not having this? Should it be backported to stable?

> Signed-off-by: Wei Liu <wei.liu2@citrix•com>
> ---
>  drivers/net/xen-netfront.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c
> index 38f9c95..01f589d 100644
> --- a/drivers/net/xen-netfront.c
> +++ b/drivers/net/xen-netfront.c
> @@ -68,7 +68,7 @@ struct netfront_cb {
>  
>  #define NET_TX_RING_SIZE __CONST_RING_SIZE(xen_netif_tx, PAGE_SIZE)
>  #define NET_RX_RING_SIZE __CONST_RING_SIZE(xen_netif_rx, PAGE_SIZE)
> -#define TX_MAX_TARGET min_t(int, NET_RX_RING_SIZE, 256)
> +#define TX_MAX_TARGET min_t(int, NET_TX_RING_SIZE, 256)
>  
>  struct netfront_stats {
>  	u64			rx_packets;
> -- 
> 1.7.8.3

  reply	other threads:[~2012-01-26 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 17:23 [PATCH] xen-netfront: correct MAX_TX_TARGET calculation Wei Liu
2012-01-26 18:19 ` Konrad Rzeszutek Wilk [this message]
2012-01-27 10:36   ` Wei Liu
2012-02-03 12:27     ` [Xen-devel] " Laszlo Ersek
2012-02-03 12:59       ` Laszlo Ersek
2012-02-03 13:26         ` Jan Beulich
2012-02-03 13:39           ` Laszlo Ersek
2012-01-26 18:48 ` David Miller

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=20120126181900.GB25572@phenom.dumpdata.com \
    --to=konrad.wilk@oracle$(echo .)com \
    --cc=ian.campbell@citrix$(echo .)com \
    --cc=jeremy@goop$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=wei.liu2@citrix$(echo .)com \
    --cc=xen-devel@lists$(echo .)xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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