From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Yevgeny Kliteynik
<kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm SA DB: dump only if modified
Date: Tue, 12 Jan 2010 16:36:00 +0200 [thread overview]
Message-ID: <20100112143600.GD574@me> (raw)
In-Reply-To: <4B4AE5B3.10504-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 10:47 Mon 11 Jan , Yevgeny Kliteynik wrote:
> Currently, if dumping SA DB is enabled, the file is dumped
> at every sweep. This patch adds "dirty" flag that denotes
> whether the SA DB needs to be dumped or not.
>
> SA DB contains 3 types of data:
> - informinfo records
> - service records
> - mcmember records
>
> So the flag must be set in 6 places:
> - add/remove informinfo record
> - add/remove service records
> - add/remove mcmember records
>
> Another possible place for setting this flag is mcgroup
> create/delete (this is sometimes duplicated by the add/remove
> mcmember records), but I think that this is not needed:
>
> The mcgroups w/o mcmembers can be created in two ways:
>
> 1. By creating well-known mcgroup for a partition.
> In this case when new instance of OSM is launched,
> the same mcgroup should be creted anyway from the
> partition configuration, so no need to force its
> duplication in the SA DB file.
>
> 2. By loading mcgroup from SA DB file.
> In this case it's either mcgroup w/o members, which
> is what's handled by (1), or it's mcgroup with members,
> butthe members just weren't loaded yet.
>
> So in both cases, no need to force SA DB dump.
>
> Signed-off-by: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Applied. Thanks.
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-12 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 8:47 [PATCH] opensm SA DB: dump only if modified Yevgeny Kliteynik
[not found] ` <4B4AE5B3.10504-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-01-12 14:36 ` Sasha Khapyorsky [this message]
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=20100112143600.GD574@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.