All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Cc: mka@chromium.org, evgreen@chromium.org, andersson@kernel.org,
	quic_cpratapa@quicinc.com, quic_avuyyuru@quicinc.com,
	quic_jponduru@quicinc.com, quic_subashab@quicinc.com,
	elder@kernel.org, netdev@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/4] net: ipa: don't use fixed table sizes
Date: Tue, 25 Oct 2022 14:51:39 -0500	[thread overview]
Message-ID: <20221025195143.255934-1-elder@linaro.org> (raw)

Currently, routing and filter tables are assumed to have a fixed
size for all platforms.  In fact, these tables can support many more
entries than what has been assumed; the only limitation is the size
of the IPA-resident memory regions that contain them.

This series rearranges things so that the size of the table is
determined from the memory region size defined in configuration
data, rather than assuming it is fixed.

This will required for IPA versions 5.0+, where the number of
entries in a routing table is larger.

					-Alex

Alex Elder (4):
  net: ipa: record the route table size in the IPA structure
  net: ipa: determine route table size from memory region
  net: ipa: don't assume 8 modem routing table entries
  net: ipa: determine filter table size from memory region

 drivers/net/ipa/data/ipa_data-v3.1.c   | 19 ++++----
 drivers/net/ipa/data/ipa_data-v3.5.1.c | 27 ++++++------
 drivers/net/ipa/data/ipa_data-v4.11.c  | 17 +++----
 drivers/net/ipa/data/ipa_data-v4.2.c   | 17 +++----
 drivers/net/ipa/data/ipa_data-v4.5.c   | 17 +++----
 drivers/net/ipa/data/ipa_data-v4.9.c   | 17 +++----
 drivers/net/ipa/ipa.h                  |  6 +++
 drivers/net/ipa/ipa_cmd.c              | 21 ++++-----
 drivers/net/ipa/ipa_data.h             |  2 +
 drivers/net/ipa/ipa_main.c             |  6 +++
 drivers/net/ipa/ipa_mem.c              |  4 +-
 drivers/net/ipa/ipa_qmi.c              |  9 ++--
 drivers/net/ipa/ipa_table.c            | 61 ++++++++++++++------------
 drivers/net/ipa/ipa_table.h            | 13 +-----
 14 files changed, 123 insertions(+), 113 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-10-25 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 19:51 Alex Elder [this message]
2022-10-25 19:51 ` [PATCH net-next 1/4] net: ipa: record the route table size in the IPA structure Alex Elder
2022-10-25 19:51 ` [PATCH net-next 2/4] net: ipa: determine route table size from memory region Alex Elder
2022-10-25 19:51 ` [PATCH net-next 3/4] net: ipa: don't assume 8 modem routing table entries Alex Elder
2022-10-25 19:51 ` [PATCH net-next 4/4] net: ipa: determine filter table size from memory region Alex Elder
2022-10-27 12:00 ` [PATCH net-next 0/4] net: ipa: don't use fixed table sizes patchwork-bot+netdevbpf

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=20221025195143.255934-1-elder@linaro.org \
    --to=elder@linaro.org \
    --cc=andersson@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=elder@kernel.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=quic_avuyyuru@quicinc.com \
    --cc=quic_cpratapa@quicinc.com \
    --cc=quic_jponduru@quicinc.com \
    --cc=quic_subashab@quicinc.com \
    /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.