From: jigsaw <jigsaw@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 答复: [PATCH] Add user defined tag calculation callback tolibrte_distributor.
Date: Fri, 7 Nov 2014 14:38:13 +0200 [thread overview]
Message-ID: <CAHVfvh6y4f7+bMhzmwOu5c0Y4wzwNaxj4sQPtq8cabGbdHrzXg@mail.gmail.com> (raw)
In-Reply-To: <20141107094521.GB4628@bricha3-MOBL3>
Hi Bruce,
>> If a tag value of zero is ever passed in, then it will start matching
against cores which are not doing any processing.
Yes, this is true according to current bookkeeping of inflight tags.
But if the slot in in_flight_tags is not a uint32_t but a struct which has
a filed as indication of "on/off", and also with corresponding changes in
looking for a matched tag, then the need for 1 bit mask can be eliminated.
Of course this change requires a little bit more, O(n), memory space and
costs O(n) more branch misses. But the benefit is a more free interface to
user app.
This is just another trade-off. Since I am in need of such freedom, I am
more interested in the free use of 32bits.
thx &
rgds,
-qinglai
On Fri, Nov 7, 2014 at 11:45 AM, Bruce Richardson <
bruce.richardson@intel.com> wrote:
> On Thu, Nov 06, 2014 at 09:52:25PM +0200, jigsaw wrote:
> > Hi Bruce,
> >
> > Actually IMHO it is good to leave the freedom to user to decide how to
> > interpret the tag value, i.e. remove the OR 1 bit.
> > If the tag value is zero, then we assume the programmer know what he is
> > doing. Of course this shall be clearly documented in the comment/doxgen.
> >
> >
> > thx &
> > rgds,
> > -qinglai
>
> I don't believe that will work. If a tag value of zero is ever passed
> in, then it will start matching against cores which are not doing any
> processing. Then it will get queued up to get sent to those cores, and so
> never get processed.
> We need a bit somewhere inside the tag to permanently set - though it can
> be configurable.
>
> /Bruce
>
> >
> > On Thu, Nov 6, 2014 at 8:01 PM, jigsaw <jigsaw@gmail.com> wrote:
> >
> > > Hi Bruce,
> > >
> > > In my use case, unfortunately the tag is not hash. And the tag can be
> on
> > > either low or high bits, depending on configuration.
> > > I wonder if it is possible to let the user to decide which bit to mask,
> > > i.e. to add another param to rte_distributor_create to define the mask.
> > >
> > > thx &
> > > rgds,
> > > -qinglai
> > >
> > > On Thu, Nov 6, 2014 at 3:59 PM, Bruce Richardson <
> > > bruce.richardson@intel.com> wrote:
> > >
> > >> On Thu, Nov 06, 2014 at 02:36:09PM +0200, Qinglai Xiao wrote:
> > >> > Hi Bruce,
> > >> >
> > >> > There is a subtle case in which tag values are 2 and 3,
> respectively.
> > >> Then these two tags cannot be distinguished. There should be a better
> way
> > >> so as to handle this situation.
> > >>
> > >> It's not just in that, case, it's in any case where a pair of tags
> differ
> > >> by
> > >> only a single bit. I've been assuming that the tag is likely to be a
> hash
> > >> value in most cases - given that it's only 32-bit - in which case it
> just
> > >> doesn't
> > >> matter which bit we chose to permanently set to 1, but if there are
> > >> scenarios
> > >> where it's likely that the low bits are used but the high ones not
> so, we
> > >> can
> > >> look to change which bit is set to 1. Either way, the distributor just
> > >> uses a
> > >> 31-bit tag rather than a 32-bit one.
> > >>
> > >> /Bruce
> > >>
> > >> >
> > >> > thx &
> > >> > rgds
> > >> > -qinglai
> > >> >
> > >> > -----原始邮件-----
> > >> > 发件人: "Thomas Monjalon" <thomas.monjalon@6wind.com>
> > >> > 发送时间: 2014/11/6 12:36
> > >> > 收件人: "Bruce Richardson" <bruce.richardson@intel.com>
> > >> > 抄送: "dev@dpdk.org" <dev@dpdk.org>; "jigsaw" <jigsaw@gmail.com>
> > >> > 主题: Re: [dpdk-dev] [PATCH] Add user defined tag calculation callback
> > >> tolibrte_distributor.
> > >> >
> > >> > 2014-11-06 09:22, Bruce Richardson:
> > >> > > On Wed, Nov 05, 2014 at 07:24:13PM +0200, jigsaw wrote:
> > >> > > >
> > >>
> http://dpdk.org/browse/dpdk/tree/lib/librte_distributor/rte_distributor.c#n285
> > >> > > >
> > >> > > > new_tag = (next_mb->hash.rss | 1);
> > >> > > >
> > >> > > > Why the logical OR is needed?
> > >> > >
> > >> > > That's needed to ensure that we never track a tag with an actual
> > >> value of zero.
> > >> > > We instead always force the low bit to be 1, so that we can use
> zero
> > >> as an
> > >> > > "empty" value.
> > >> >
> > >> > Bruce, could you check how this code may be better commented please?
> > >> > This discussion shows that the distributor library probably needs
> more
> > >> > explanations in the code or doxygen.
> > >> >
> > >> > Thanks
> > >> > --
> > >> > Thomas
> > >>
> > >
> > >
>
next prev parent reply other threads:[~2014-11-07 12:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 13:30 [dpdk-dev] [PATCH] Add user defined tag calculation callback to librte_distributor Qinglai Xiao
2014-11-05 14:27 ` Bruce Richardson
2014-11-05 15:11 ` jigsaw
2014-11-05 16:36 ` Bruce Richardson
2014-11-05 17:24 ` jigsaw
2014-11-06 9:22 ` Bruce Richardson
2014-11-06 10:14 ` jigsaw
2014-11-06 10:36 ` Thomas Monjalon
2014-11-06 12:36 ` [dpdk-dev] 答复: [PATCH] Add user defined tag calculation callback tolibrte_distributor Qinglai Xiao
2014-11-06 13:59 ` Bruce Richardson
2014-11-06 18:01 ` jigsaw
2014-11-06 19:52 ` jigsaw
2014-11-07 9:45 ` Bruce Richardson
2014-11-07 12:38 ` jigsaw [this message]
2014-11-07 13:53 ` Bruce Richardson
2014-11-07 14:31 ` jigsaw
[not found] ` <20141107144410.GC12092@bricha3-MOBL3>
2014-11-07 14:52 ` jigsaw
2014-11-07 15:04 ` Bruce Richardson
2014-11-07 15:18 ` jigsaw
2014-11-06 13:55 ` [dpdk-dev] [PATCH] distributor: add comments to make code more readable Bruce Richardson
2014-11-07 14:08 ` Thomas Monjalon
2014-11-07 14:31 ` jigsaw
2014-11-06 13:57 ` [dpdk-dev] [PATCH] Add user defined tag calculation callback to librte_distributor Bruce Richardson
2014-11-05 15:13 ` Ananyev, Konstantin
2014-11-05 15:24 ` jigsaw
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=CAHVfvh6y4f7+bMhzmwOu5c0Y4wzwNaxj4sQPtq8cabGbdHrzXg@mail.gmail.com \
--to=jigsaw@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).