public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Advice with adding RPS/RFS for PPP connections
Date: Mon, 01 Jun 2020 10:36:25 +0100	[thread overview]
Message-ID: <A3BCB344-C4AE-4A36-BB49-6FECED30EE07@ipfire.org> (raw)
In-Reply-To: <CACy04wP7LrrXuiaetF3inEeuwzokZ3KkHKUrVNyM+9MHiPx5+A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

Hello Adam,

Thank you for getting in touch.

> On 29 May 2020, at 21:18, Adam Jaremko <adam.jaremko+ipfire(a)gmail.com> wrote:
> 
> I've been doing RPS/RFS in my own shell scripts for some time and also implemented primitive support into the web UI but I'm very much a perl novice since my last real usage was in the 90's.

What did you change in your scripts?

> First and foremost, would it be relevant to add such support in an official capacity?

Generally I would say yes. Does it come with any downsides?

I am not aware that anyone ran into resource issues here, because PPP connections are usually rather slow (up to 100 MBit/s). But we would probably gain some throughput by better utilisation of the load-balancing on the IPS, etc.

> Second, is there any guidelines to accessing the filesytem with the scripts? I ask because my non thorough browsing of the code only revealed the use of readhash, whereas I would need to poke and prod at procfs to work with complex CPU affinity per queue.

What are you doing here? Are you assigning a processor to a queue using that script?

> I can submit a review patch of my primitive implementation (non NUMA) wherein it's the same CPU affinity used across each queue using nproc and some check boxes just to get feedback and a start in the right direction.
> 
> Thanks,
> AJ

-Michael

       reply	other threads:[~2020-06-01  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACy04wP7LrrXuiaetF3inEeuwzokZ3KkHKUrVNyM+9MHiPx5+A@mail.gmail.com>
2020-06-01  9:36 ` Michael Tremer [this message]
2020-06-02  1:38   ` Adam Jaremko
2020-06-02  7:52     ` Michael Tremer
2020-06-03 15:27       ` Adam Jaremko

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=A3BCB344-C4AE-4A36-BB49-6FECED30EE07@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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