All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: Ronald Pina <pinaronald@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Allow controlling NAPI weight of virtual network interfaces (vif) with sysfs
Date: Fri, 13 Mar 2015 17:03:14 +0000	[thread overview]
Message-ID: <55031852.4080606@linaro.org> (raw)
In-Reply-To: <CAONBAacexniK1r8wbhVM3z+7KkCKtCQxru-xc9biSPk+UTiB=w@mail.gmail.com>

Hi,

I reckon you want to do this for the same reason you started this thread 
a month ago:

http://lists.xen.org/archives/html/xen-devel/2015-02/msg00228.html

Have you considered the suggestions given there? (using the existing 
traffic shaping facilities of the kernel). As Wei said, you would have 
better luck with them than introducing a core networking driver feature 
which might be redundant?

Regards,

Zoltan

On 13/03/15 11:11, Ronald Pina wrote:
> Hello
> I am working to allow controlling napi weight of virtual interfaces on
> xen using sysfs.
> If may i ask, is it achievable since NAPI interface structure in
> current kernels is managed by the driver?
>
> Please, any help or idea is very appreciated.
> Best Regards
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

  parent reply	other threads:[~2015-03-13 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 11:11 Allow controlling NAPI weight of virtual network interfaces (vif) with sysfs Ronald Pina
2015-03-13 11:30 ` Wei Liu
2015-03-13 11:56   ` Ronald Pina
2015-03-13 12:05     ` Wei Liu
2015-03-13 12:49       ` Ronald Pina
2015-03-13 13:53         ` Wei Liu
2015-03-13 17:03 ` Zoltan Kiss [this message]
2015-03-13 19:05   ` Ronald Pina
2015-03-16 11:49     ` Zoltan Kiss
2015-03-17 11:11       ` Ronald Pina

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=55031852.4080606@linaro.org \
    --to=zoltan.kiss@linaro.org \
    --cc=pinaronald@gmail.com \
    --cc=xen-devel@lists.xen.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.