From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.com>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/4] common: Add function for selecting from different output files
Date: Wed, 18 Nov 2015 16:37:14 +0100 [thread overview]
Message-ID: <20151118153714.GH6097@quack.suse.cz> (raw)
In-Reply-To: <20151116212924.GL14311@dastard>
On Tue 17-11-15 08:29:24, Dave Chinner wrote:
> On Wed, Nov 04, 2015 at 05:31:37PM +0100, Jan Kara wrote:
> > Add function for selection of different output files. The idea is that
> > in config file ($seq.cfg) there are several lines like:
> >
> > feat1,feat2: suffix
> >
> > The function is passed a feature string (or uses MOUNT_OPTIONS if no
> > argument is passed) and selects output file with a suffix for which all
> > features are present in the feature string. If there is no matching
> > line, output with 'default' suffix is selected.
> >
> > Signed-off-by: Jan Kara <jack@suse.com>
>
> Looks like a good idea, but probably needs to be integrated into
> _link_out_file(), which already does platform based output file
> linking...
OK, will do.
> > ---
> > common/rc | 41 +++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 41 insertions(+)
> >
> > diff --git a/common/rc b/common/rc
> > index adf1edf64d8d..543780c92c59 100644
> > --- a/common/rc
> > +++ b/common/rc
> > @@ -3142,6 +3142,47 @@ get_block_size()
> > echo `stat -f -c %S $1`
> > }
> >
> > +_select_output()
> > +{
> > + if [ $# -eq 0 ]; then
> > + FEATURES=${MOUNT_OPTIONS##"-o "}
> > + else
> > + FEATURES=$1
> > + fi
> > +
> > + export FEATURES
> > + seqfull=$SRC_DIR/$seqnum
> > + perl -e '
> > + my %feathash;
> > + my $feature, $result, $suffix, $opts;
> > +
> > + foreach $feature (split(/,/, $ENV{"FEATURES"})) {
> > + $feathash{$feature} = 1;
> > + }
> > + $result = "default";
> > + while (<>) {
> > + my $found = 1;
> > +
> > + chomp;
> > + ($opts, $suffix) = split(/ *: */);
> > + foreach my $opt (split(/,/, $opts)) {
> > + if (!exists($feathash{$opt})) {
> > + $found = 0;
> > + last;
> > + }
> > + }
> > + if ($found == 1) {
> > + $result = $suffix;
> > + last;
> > + }
> > + }
> > + print $result
> > + ' <$seqfull.cfg | {
> > + read SUFFIX
> > + ln -fs $seq.out.$SUFFIX $seqfull.out
> > + }
> > +}
>
> I'd much prefer the perl code simply returns the appropriately
> matched suffix and then the shell code does the linking of the
> output file. That way other things that the test harness is aware of
> can also be taken into account.
Well, the perl code does return (print) the selected suffix. But I guess
you dislike the piping into a shell block where the linking happens. I
wanted to save on some shell escaping but it actually won't be that bad.
I'll remove the pipe.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2015-11-18 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:31 [PATCH 0/4] Output selection, improvements for ext4/001 Jan Kara
2015-11-04 16:31 ` [PATCH 1/4] _filter_fiemap: Avoid awk interval regexps Jan Kara
2015-11-04 16:31 ` [PATCH 2/4] ext4/001: Update output Jan Kara
2015-11-04 16:31 ` [PATCH 3/4] common: Add function for selecting from different output files Jan Kara
2015-11-16 21:29 ` Dave Chinner
2015-11-18 15:37 ` Jan Kara [this message]
2015-11-04 16:31 ` [PATCH 4/4] ext4/001: Select different output based on mount options Jan Kara
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=20151118153714.GH6097@quack.suse.cz \
--to=jack@suse.cz \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.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