From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 07/11] flow: Introduce 'sidx' type to represent one side of one flow
Date: Thu, 30 Nov 2023 11:37:40 +1100 [thread overview]
Message-ID: <ZWfZVI0OD-7DdoYW@zatzit> (raw)
In-Reply-To: <20231129153232.6abfe53c@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On Wed, Nov 29, 2023 at 03:32:32PM +0100, Stefano Brivio wrote:
> On Mon, 27 Nov 2023 10:33:44 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > In a number of places, we use indices into the flow table to identify a
> > specific flow. We also have cases where we need to identify a particular
> > side of a particular flow, and we expect those to become more common as
> > we generalise the flow table to cover more things.
> >
> > To assist with that, introduces flow_sidx_t, an index type which identifies
> > a specific side of a specific flow in the table.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > flow.h | 13 +++++++++++++
> > flow_table.h | 36 ++++++++++++++++++++++++++++++++++++
> > 2 files changed, 49 insertions(+)
> >
> > diff --git a/flow.h b/flow.h
> > index b6da516..3c90bbd 100644
> > --- a/flow.h
> > +++ b/flow.h
> > @@ -39,6 +39,19 @@ struct flow_common {
> > #define FLOW_TABLE_PRESSURE 30 /* % of FLOW_MAX */
> > #define FLOW_FILE_PRESSURE 30 /* % of c->nofile */
> >
> > +/**
> > + * struct flow_sidx - ID for one side of a specific flow
> > + * @side: Side referenced (0 or 1)
> > + * @flow: Index of flow referenced
> > + */
> > +typedef struct flow_sidx {
>
> Implying my usual argument :) ...is there any advantage over using this
> simply as a struct?
So, usually I too would prefer to use a struct as a struct, without a
typedef. The reason I'm doing differently here, is that I want to
emphasise that for many purposes this can be treated like an index, in
particular that it's small and trivially copyable. In particular it
should be passed by value, passing by reference would be silly.
That's kind of the opposite of what one tends to be conveying by
reminding users that they're working with a struct.
>
> > + int side :1;
> > + unsigned flow :FLOW_INDEX_BITS;
> > +} flow_sidx_t;
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-30 0:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 23:33 [PATCH v2 00/11] Introduce unified flow table, first steps David Gibson
2023-11-26 23:33 ` [PATCH v2 01/11] flow, tcp: Generalise connection types David Gibson
2023-11-26 23:33 ` [PATCH v2 02/11] flow, tcp: Move TCP connection table to unified flow table David Gibson
2023-11-26 23:33 ` [PATCH v2 03/11] flow, tcp: Consolidate flow pointer<->index helpers David Gibson
2023-11-26 23:33 ` [PATCH v2 04/11] util: MAX_FROM_BITS() should be unsigned David Gibson
2023-11-26 23:33 ` [PATCH v2 05/11] flow: Make unified version of flow table compaction David Gibson
2023-11-26 23:33 ` [PATCH v2 06/11] flow, tcp: Add logging helpers for connection related messages David Gibson
2023-11-26 23:33 ` [PATCH v2 07/11] flow: Introduce 'sidx' type to represent one side of one flow David Gibson
2023-11-29 14:32 ` Stefano Brivio
2023-11-30 0:37 ` David Gibson [this message]
2023-11-30 9:21 ` Stefano Brivio
2023-12-01 0:10 ` David Gibson
2023-11-26 23:33 ` [PATCH v2 08/11] tcp: Remove unneccessary bounds check in tcp_timer_handler() David Gibson
2023-11-29 14:32 ` Stefano Brivio
2023-11-30 0:42 ` David Gibson
2023-11-26 23:33 ` [PATCH v2 09/11] flow,tcp: Generalise TCP epoll_ref to generic flows David Gibson
2023-11-26 23:33 ` [PATCH v2 10/11] tcp_splice: Use unsigned to represent side David Gibson
2023-11-26 23:33 ` [PATCH v2 11/11] flow,tcp: Use epoll_ref type including flow and side David Gibson
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=ZWfZVI0OD-7DdoYW@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).